Return
-
Title
Blackout does not account for Daylight Savings time change -
Description
A user scheduled Blackout prevents alarms for 3 hours and 48 minutess starting at 2am on Sunday. During the Spring time change weekend, alarms were stopped until 6:48 AM instead of 5:48 AM. -
Cause
For many software applications, the process works like this"In the North American Eastern Standard Time Zone, DST starts on the second Sunday of March at 2:00 a.m.; the time springs forward one hour to 3:00 a.m.Events that are scheduled to run during the spring-forward transition period (2:00 a.m. to 3:00 a.m. on the day spring forward occurs) run immediately after the transition at 3:00 a.m.For example, Event A is scheduled at 2:30 a.m. on March 11, 2007. At 01:59:59 a.m., the time springs forward to 3:00 a.m. At 3:00 a.m., the server considers Event A overdue and triggers the Event immediately.At the job level, if a job has a submission time of 2:30 a.m., the server submits the job at 3:00 a.m. (assuming all other dependencies have been met)." -
Resolution
When the Windows server time reaches 2am on a time change in the Spring, it should then jump to 3am automatically. If the blackout was configured for a time length, then it should still function for the duration that was set.For example, from the FMS log, normally rollups happen at 2am every night (before and after the time change)2021-03-13 02:00:00.008 VERBOSE [QuartzScheduler.PersistencePolicy_Worker-1] com.quest.nitro.service.persistence.management.DatabaseMaintenanceController - The DatabaseMaintenance database maintenance operation started at 3/13/21 2:00 AM.and2021-03-15 02:00:00.013 VERBOSE [QuartzScheduler.PersistencePolicy_Worker-1] com.quest.nitro.service.persistence.management.DatabaseMaintenanceController - The DatabaseMaintenance database maintenance operation started at 3/15/21 2:00 AM.Since there is no 2am on a time change weekend, everything for 2am began at 3am2021-03-14 01:58:44.110 VERBOSE [org.springframework.scheduling.quartz.SchedulerFactoryBean#0_Worker-7] com.quest.nitro.service.alarm.AlarmAggregationService - Successfully synchronized the alarm state (added: 0, removed 0 alarms).2021-03-14 03:00:00.022 VERBOSE [QuartzScheduler.PersistencePolicy_Worker-1] com.quest.nitro.service.persistence.management.DatabaseMaintenanceController - The DatabaseMaintenance database maintenance operation started at 3/14/21 3:00 AM.