You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We get the current time using CLOCK_REALTIME. This reflects the current date and time, which can be adjusted by the system (e.g. NTP synchronization or manual change by the administrator).
We use the heartbeat signal to compare the current timestamp with the last seen timestamp of the opposite node to determine if the connection is lost. However, if the system time is suddenly jumped by NTP or the administrator, the difference between the current timestamp and the last seen timestamp may be greater than a threshold even if the connection is not lost.
This can be avoided by using CLOCK_MONOTONIC instead of CLOCK_REALTIME.
The text was updated successfully, but these errors were encountered:
Please describe what you would like to see
We get the current time using CLOCK_REALTIME. This reflects the current date and time, which can be adjusted by the system (e.g. NTP synchronization or manual change by the administrator).
We use the heartbeat signal to compare the current timestamp with the last seen timestamp of the opposite node to determine if the connection is lost. However, if the system time is suddenly jumped by NTP or the administrator, the difference between the current timestamp and the last seen timestamp may be greater than a threshold even if the connection is not lost.
This can be avoided by using CLOCK_MONOTONIC instead of CLOCK_REALTIME.
The text was updated successfully, but these errors were encountered: