You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Scherbakov (Jira)" <ji...@apache.org> on 2025/01/08 09:41:00 UTC

[jira] [Assigned] (IGNITE-23712) Avoid clock tick on RW requests

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

Alexey Scherbakov reassigned IGNITE-23712:
------------------------------------------

    Assignee: Alexey Scherbakov

> Avoid clock tick on RW requests
> -------------------------------
>
>                 Key: IGNITE-23712
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23712
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Scherbakov
>            Assignee: Alexey Scherbakov
>            Priority: Major
>              Labels: ignite-3
>
> Currently all RW requests (except upsert, was fixed under IGNITE-23303) use HLC.now() for timestamp.
> Actually, this is not required and doesn't affect ordering guaranties, because we only need remote HLC value for assigning (receiving in case of full transaction) commit timestamp.
> Proper order is provided by locking, and the response will always have timestamp greater or equal to latest committed dependent transaction
> tx.startTime can be used, for example.



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