[
https://issues.apache.org/jira/browse/IGNITE-19888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-19888:
---------------------------------------
Description:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
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.
*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.
was:
*Motivation*
Read timestamp for RO transaction is supposed to determine with taking into
client timestamp to linearize client transactions.
*Implementation notes*
Add client-side property to store client time {{HybridTimestamp}}
Pass the client time in TX_BEGIN request
Calculate read timestamp in server-side {{max(clientTime, now() -
idelSafeTimePropagetaionFreqency)}}
Use method with explicit timestamp to start RO transaction (the method is
implemented in IGNITE-19887)
> Add client timestamp
> --------------------
>
> 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*
> 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.
> *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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
