Closed afurche closed 3 months ago
Even without timedrift, the extension restart issue could still replicate, due to lack of "safety buffer"
Example:
{ "configId":"4b4660ab-426f-370c-b206-f440a28ecdec","taskId":"2728623243455997848","PID":"N/A", "executionStatuses":[{"status":"OK","message":"OK","timestamp":"2024-07-30 07:37:51.739 UTC"}], "processStatuses":[ {"status":"STARTUP_SCHEDULED","message":"Datasource startup in 0 minutes","timestamp":"2024-07-30 07:38:12.821 UTC"}, {"status":"TIMED_OUT_RESTART","message":"No keepalive from datasource python. Restarting","timestamp":"2024-07-30 07:37:51.738 UTC"} ] }
In the example above, the heartbeat was received at 07:37:51.739, but EEC scheduled restart at 07:37:51.738
07:37:51.739
07:37:51.738
Even without timedrift, the extension restart issue could still replicate, due to lack of "safety buffer"
Example:
In the example above, the heartbeat was received at
07:37:51.739
, but EEC scheduled restart at07:37:51.738