[jira] [Commented] (IGNITE-17999) Incorrect handling of TxStateReplicaRequest

["Vladislav Pyatkov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681155#comment-17681155 ] 

Vladislav Pyatkov commented on IGNITE-17999:
--------------------------------------------

The main part of the issue will be fixed in IGNITE-18524 epic.

> Incorrect handling of TxStateReplicaRequest
> -------------------------------------------
>
>                 Key: IGNITE-17999
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17999
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation:*
> After observation, the following points were highlighting to fix:
> # The request has a property named is commitTimestamp, but it is not a time to commit. This property should be renamed to readTimestamp, because it is a time with which a transaction tries to read another transaction state (to read an entry).
> # The request should to be handled by a primary replica (presently, it is handled by leader, that can be a different node).
> *Definition of done:*
> # Property {{TxStateReplicaRequest#commitTimestamp}} should change to {{TxStateReplicaRequest#readTimestamp}}.
> # Because {{TxStateReplicaRequest}} is sent from {{PlacementDriver}}, there is no a reference to the raft client, the sending will be happening to the node from an assignment. It {{PrimaryReplicaMissException}} will be caught, the request should be resent to next node from the assignment.



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