-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
Sprint 179, Sprint 180, Sprint 181, Sprint 182
-
17
-
Introduce unified time management in all Onedata components - all clusters now regularly synchronize their clocks with the Onezone service, the process is managed by Onepanel's master node.
-
Include to Changelog
There are some places where different methods of acquiring timestamps are used - e.g. erlang:timestamp or os:timestamp in monitoring and datastore internals.
look for TODOs with the ticket numer in code, at least in cluster-worker, op-worker, onepanel
WARNING - when clock is used to measure time differences, there can be bad reads if sync was done in the meantime - consider adding an API like start_timer, stop_timer