[
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 necessary to adjust the clock when processing
{{TimestampAware}} messages in sql-engine's {{MessageService}}. so currently
each component must duplicate the clock adjusting logic.
*Also* as part of this task it would be nice to fix the behavior of SQL so that
it does NOT update the clock for READ ONLY operations.
was:
{{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 necessary to adjust the clock when processing
{{TimestampAware}} messages in sql-engine's {{MessageService}}. so currently
each component must duplicate the clock adjusting logic.
*Also* as part of this task it would be nice to fix the behavior of sql-engine
so that it does NOT update the clock for READ ONLY operations.
> 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 necessary to adjust the clock when processing
> {{TimestampAware}} messages in sql-engine's {{MessageService}}. so currently
> each component must duplicate the clock adjusting logic.
> *Also* as part of this task it would be nice to fix the behavior of SQL so
> that it does NOT update the clock for READ ONLY operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
