[
https://issues.apache.org/jira/browse/IGNITE-21552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823927#comment-17823927
]
Pavel Pereslegin commented on IGNITE-21552:
-------------------------------------------
[~korlov], [~amashenkov], please review the proposed changes.
> Sql. Update clock on query initiator node
> ------------------------------------------
>
> Key: IGNITE-21552
> URL: https://issues.apache.org/jira/browse/IGNITE-21552
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As for now, neither of sql messages update the hybrid clock. This may result
> in violation of transactional protocol, since commit timestamp is calculated
> on initiator node, and the clock may be behind those on nodes which processed
> transactional request.
> Since precise time is crucial only to calculate commit timestamp, to reduce
> contention on the clock it's proposed to propagate timestamp only on
> {{QueryBatchMessage}}.
> See {{org.apache.ignite.internal.replicator.message.TimestampAware}} for
> example of time propagation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
