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

Pavel Pereslegin updated IGNITE-21709:
--------------------------------------
    Description: 
{{TimestampAware}} messages contain hybrid timestamp to adjust a hybrid logical 
clock.

Currently, ReplicaManager updates the local clock when it receives a 
{{ReplicaRequest}} with a timestamp.

It may be worth revising the design and adding general processing of such 
messages (probably at the {{MessagingService}} level).
For example, it is also necessary to adjust the clock when receiving a 
{{QueryBatchMessage}} (sql-engine) and currently each component must duplicate 
the clock adjusting logic.


  was:
{{TimestampAware}} messages contain timestamp to adjust a hybrid logical clock.

Currently, ReplicaManager updates the local clock when it receives a 
{{ReplicaRequest}} with a timestamp.

It may be worth revising the design and adding general processing of such 
messages (probably at the {{MessagingService}} level).
For example, it is also necessary to adjust the clock when receiving a 
{{QueryBatchMessage}} (sql-engine) and currently each component must duplicate 
the clock adjusting logic.



> Revise TimestampAware messages processing
> -----------------------------------------
>
>                 Key: IGNITE-21709
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21709
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> {{TimestampAware}} messages contain hybrid timestamp to adjust a hybrid 
> logical clock.
> Currently, ReplicaManager updates the local clock when it receives a 
> {{ReplicaRequest}} with a timestamp.
> It may be worth revising the design and adding general processing of such 
> messages (probably at the {{MessagingService}} level).
> For example, it is also necessary to adjust the clock when receiving a 
> {{QueryBatchMessage}} (sql-engine) and currently each component must 
> duplicate the clock adjusting logic.



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

Reply via email to