[ 
https://issues.apache.org/jira/browse/IGNITE-26121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Lapin updated IGNITE-26121:
-------------------------------------
    Description: 
h3. Motivation

For more context please check https://issues.apache.org/jira/browse/IGNITE-25645

If a node receives a message from the future with a time difference between the 
message and the local time on the node by more than MAX_CLOCK_SKEW, then this 
clearly indicates that the maximum allowed delta has been exceeded and thus we 
should print a warning message to the log.
h3. Definition of Done
 * If the maximum allowed clock drift has been exceeded, the node that detects 
this prints warning message to the log.

h3. Implementation Notes
 * The best place to do that is either ClockServiceImpl where we do have 
maxClockSkewMsSupplier or even HybridClockImpl itself in order to prevent 
excessive System.currentTimeMillis() calls.

> Print warning message if MAX_CLOCK_SKEW exceeded
> ------------------------------------------------
>
>                 Key: IGNITE-26121
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26121
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> For more context please check 
> https://issues.apache.org/jira/browse/IGNITE-25645
> If a node receives a message from the future with a time difference between 
> the message and the local time on the node by more than MAX_CLOCK_SKEW, then 
> this clearly indicates that the maximum allowed delta has been exceeded and 
> thus we should print a warning message to the log.
> h3. Definition of Done
>  * If the maximum allowed clock drift has been exceeded, the node that 
> detects this prints warning message to the log.
> h3. Implementation Notes
>  * The best place to do that is either ClockServiceImpl where we do have 
> maxClockSkewMsSupplier or even HybridClockImpl itself in order to prevent 
> excessive System.currentTimeMillis() calls.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to