Enhancing Scalability with Master Scheduler
This topic describes the behavior of the Process Scheduler sever in various fail over situations to provide you with some reasonable expectations of scalability in comparable situations.
Scenario |
System Behavior |
---|---|
No Master Scheduler configured or running. |
|
One or more Master Scheduler servers running. |
|
Two or more Master Scheduler servers are configured. |
If one Master Scheduler is down, the other will become master scheduler automatically |
Master Scheduler available and one of the servers is overloaded. |
Work load on overloaded server will be distributed to other servers as per configuration. |
Master Scheduler is available, and one Process Scheduler server is brought down, while processing a request. |
Note: The items above assume that the Process Scheduler severs is shut down using PSADMIN, using the normal shut down option, not the forced shut down option. If the forced shut down option is selected, the running process (running at the time of shutting down) will be killed. |
Process Scheduler is brought down when it has a number of processes queued for processing. |
Queued processes will be transferred to other available servers depending on configuration. |
Note: The above items assume that web server is always up. If it is down, report distribution can be disrupted.
Note: Abrupt/forcible killing of servers using utilities like Task Manager of forced shut down using PSADMIN may lead to irrecoverable change of state of a running processes.
Note: All configured Master Scheduler servers should not shut down at the same time. The above statements assume that, at any given time, at least one Master Scheduler server is up and running.