Scheduling custom interval incorrect processing after winter time change

XMLWordPrintable

    • Sprint 27, Sprint 28, Sprint 29, Sprint 30, Sprint 31, Sprint 32, Sprint 33, Sprint 34, Sprint 35
    • 1

      Steps to reproduce:
      Change timezone on server:

      date -s "29 OCT 2017 03:50:00 EEST"
      

      Create item with configuration like on screenshot with example (update interval 0, scheduling interval "m0-59").
      wait till timezone will be changed to EET (timezone should be changed at 04:00 EEST)
      Result:

      mysql> select itemid,count(*) from history group by itemid;
      +--------+----------+
      | itemid | count(*) |
      +--------+----------+
      |  25366 |    46427 |
      |  25367 |   364358 |
      +--------+----------+
      2 rows in set (0.12 sec)
      

      Expected:
      The item should be processed with one minute time interval, but scheduling interval does not work properly after winter time change and generates many duplicate values in DB.

            Assignee:
            Andris Zeila
            Reporter:
            Alexey Pustovalov
            Team A
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: