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

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2023/11/29 10:30:00 UTC

[jira] [Commented] (IGNITE-20875) Add enlistment consistency token to PrimaryReplicaRequest interface

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

Alexander Lapin commented on IGNITE-20875:
------------------------------------------

[~v.pyatkov] LGTM

> Add enlistment consistency token to PrimaryReplicaRequest interface
> -------------------------------------------------------------------
>
>                 Key: IGNITE-20875
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20875
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> h3. Motivation
> The procedure in the method PartitionReplicaListener#ensureReplicaIsPrimary looks not simple because we have no interface that provides the enlistment consistency id. But PrimaryReplicaRequest well-suited for the role because it is used to determine messages targeted at the primary replica.
> h3. Definition of done
> All messages that are certain to the primary replica should include the PrimaryReplicaTestRequest interface. The interface should have the enlistment consistency token internally.



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