[jira] [Updated] (IGNITE-19888) Add tracking of last observed transaction timestamp to client

["Igor Sapego (Jira)" <ji...@apache.org>]

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

Igor Sapego updated IGNITE-19888:
---------------------------------
    Summary: Add tracking of last observed transaction timestamp to client  (was: Add client timestamp)

> Add tracking of last observed transaction timestamp to client
> -------------------------------------------------------------
>
>                 Key: IGNITE-19888
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19888
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> Read timestamp for RO transaction is supposed to determine with taking into client timestamp to linearize client transactions.
> *Implementation notes*
> Responses, which start RO transaction (IGNITE-19887) and commit RW transaction (IGNITE-19886), have to provide a timestamp.
> If a server response does not have the timestamp or timestamp is less than the client already has, do nothing.
> If the time is grater than the client has, the client timestamp should be updated.
> The timestamp is used to start RO transaction (IGNITE-19887)
> *Definition of done*
> The timestamp is passed from the server-side to a client. The client just save the timestamp and send it in each request to server-side.
> All client-side created RO transactions should execute in past with timestamp has been determining by client timestamp.



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