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

Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2024/01/09 09:11:00 UTC

[jira] [Commented] (IGNITE-21209) Do not try handle PrimaryReplicaMissException on transaction operation

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

Vladislav Pyatkov commented on IGNITE-21209:
--------------------------------------------

Meregd 57da4e559cf20e06fcaef419cb7d77822534e3b7

> Do not try handle PrimaryReplicaMissException on transaction operation
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-21209
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21209
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> h3.  Motivation
> A transaction enlists a primary replica before making an operation request. But the PrimaryReplicaMissException can be thrown after the request tries to be sent. This means that any ties to remap the request cannot enlist a new primary replica, and all this is meaningless. The code, which handles the PrimaryReplicaMissException, just wastes time.
> h3. Definition of done
> Do not handle the PrimaryReplicaMissException on any transaction operation after the primary replica is already enlisted.



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