Dear SQLIters,

I use datetime('now') to record when a job gets started and stopped. As soon as 
a job stops, new is started. Thus stop of the previous should be within a 
second of the start of the next, as you see in the first few lines. But then 
the clock jumps.

Job 1847 ends at 16:44:11 and job 1852 starts at 18:47:46 (and actually 
subsequently dies as evidenced by its stop being NULL). Next job, 2283, is 
started BEFORE job 1852. RunID is INTEGER PRIMARY KEY and for this purpose is 
auto incrementing. Jobs are also running on other nodes, therefore runID is not 
contiguous for this node.


runID      hostname   start               stop
---------- ---------- ------------------- -------------------
1841       loginnode4 2018-05-14 07:53:42 2018-05-14 10:05:41
1843       loginnode4 2018-05-14 10:05:41 2018-05-14 12:18:05
1845       loginnode4 2018-05-14 12:18:05 2018-05-14 14:30:50
1847       loginnode4 2018-05-14 14:30:50 2018-05-14 16:44:11
1852       loginnode4 2018-05-14 18:47:56
2283       loginnode4 2018-05-15 18:18:59

Could it indicate other issues than the clock itself? It is highly unlikely 
that clock happened to jump forward at the time when 1852 was finishing (at 
16:44:11). Time of start of 2283 looks correct, agrees with my watch, because I 
started this job manually.

Roman
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to