Introduction:
For information about how scheduling works in a Strategy Intelligence Server 9.x. cluster, refer to the following Strategy Knowledge Base document:
KB30775: How are time-based and event-based schedules executed in a clustered Strategy Server environment?
Consider a Strategy Intelligence Server 9.x cluster where both the nodes are in different time zones. One node (Node A) is on EST (US Standards) and one nodes is on CST (US Standards).
Consider that the current time is 6:00PM on Node A and the 5:00PM on Node B. A user connects to Node B using Strategy Developer 9.x and creates a schedule called ScheduleA that is supposed to kick off at 7:00 PM (i.e. 2 hours away from the current time on Node B)
When does schedule A kick off?
The time at which scheduleA will kick off will depend on, which node is the primary node in the cluster. If Node A is the primary node in the cluster, the schedule will kick off at 7:00 PM (EST) which is still 6:00 PM (CST). If Node B is primary node in the cluster, then the schedule will kick off at 7:00 PM (CST).
Time based schedules always kick off as per the time of the primary node in the cluster. This might not always match with the user's expectations who created the schedule. This is because, the time that a user will see on Strategy Developer 9.x when creating the schedule will correspond to the local time of the Strategy Intelligence Server 9.x and later that the user connects to, as shown below.
Note that even though the schedule kicks off on the primary node, the jobs still get load balanced across the cluster.
