[
https://issues.apache.org/jira/browse/IGNITE-13015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13015:
--------------------------------------
Description:
Make sure node failure detection do not use:
{code:java}
System.currentTimeMillis()
and
IgniteUtils.currentTimeMillis()
{code}
We should use nano time instead. Disadventages of current impl.:
1) System time has no quarantine of strict forward movement. System time
can be adjusted, synchronized by NTP as example. This can lead to incorrect and
negative delays.
2) IgniteUtils.currentTimeMillis() is granulated by 10ms
was:
Make sure in node failure detection not used:
{code:java}
System.currentTimeMillis()
and
IgniteUtils.currentTimeMillis()
{code}
Disadventages:
1) Current system time has no quarantine of strict forward movement.
System time can be adjusted, synchronized by NTP as example. This can lead to
incorrect and negative delays.
2) IgniteUtils.currentTimeMillis() is granulated by 10ms
> Use nano time in node failure detection.
> ----------------------------------------
>
> Key: IGNITE-13015
> URL: https://issues.apache.org/jira/browse/IGNITE-13015
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
> Labels: iep-45
>
> Make sure node failure detection do not use:
> {code:java}
> System.currentTimeMillis()
> and
> IgniteUtils.currentTimeMillis()
> {code}
> We should use nano time instead. Disadventages of current impl.:
> 1) System time has no quarantine of strict forward movement. System time
> can be adjusted, synchronized by NTP as example. This can lead to incorrect
> and negative delays.
> 2) IgniteUtils.currentTimeMillis() is granulated by 10ms
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
