[
https://issues.apache.org/jira/browse/IGNITE-23719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901459#comment-17901459
]
Vladislav Pyatkov edited comment on IGNITE-23719 at 11/27/24 12:08 PM:
-----------------------------------------------------------------------
We probably can get rid of HLC _now_ invocation here:
{code}org.apache.ignite.internal.tx.impl.TxManagerImpl#commitTimestamp {code}
because we already increment HLC in _update_ invocation (when receiving
response from transaction participants). There is no reason to increment HLC
more.
was (Author: v.pyatkov):
We probably can get rid of HLC now invocation here:
{code}org.apache.ignite.internal.tx.impl.TxManagerImpl#commitTimestamp {code}
because we already increment HLC in _update_ invocation (when receiving
response from transaction participants). There is no reason to increment HLC
more.
> Delay HLC clock update for intermediate txn requests
> ----------------------------------------------------
>
> Key: IGNITE-23719
> URL: https://issues.apache.org/jira/browse/IGNITE-23719
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Scherbakov
> Priority: Major
> Labels: ignite-3
>
> Currently HLC ts from a response is applied for a RW transaction on each
> response, received by coordinator.
> This can be optimized by tracking max visible HLC in transaction's volatile
> state from all enlisted partitions until commit, and apply this value once
> before commit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
