[
https://issues.apache.org/jira/browse/IGNITE-23712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Scherbakov updated IGNITE-23712:
---------------------------------------
Description:
Currently all RW requests (except upsert , see 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.
was:
Currently all RW requests 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.
> 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
> Priority: Major
> Labels: ignite-3
>
> Currently all RW requests (except upsert , see 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)
