You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2022/09/02 08:55:00 UTC
[jira] [Updated] (IGNITE-17616) Check the replica is a primary before processing ReadWriteReplicaRequest, TxFinishReplicaRequest и TxCleanupReplicaRequest
[ https://issues.apache.org/jira/browse/IGNITE-17616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Uttsel updated IGNITE-17616:
-----------------------------------
Summary: Check the replica is a primary before processing ReadWriteReplicaRequest, TxFinishReplicaRequest и TxCleanupReplicaRequest (was: Check the replica is a primary before processing TxFinishReplicaRequest и TxCleanupReplicaRequest)
> Check the replica is a primary before processing ReadWriteReplicaRequest, TxFinishReplicaRequest и TxCleanupReplicaRequest
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-17616
> URL: https://issues.apache.org/jira/browse/IGNITE-17616
> Project: Ignite
> Issue Type: Improvement
> Reporter: Sergey Uttsel
> Assignee: Sergey Uttsel
> Priority: Major
> Labels: ignite-3, transaction3_rw
>
> Now we check that the replica is a primary on all of ReplicaRequest. But we need to check it only for ReadWriteReplicaRequest, because ReadOnlyReplicaRequest can be handled on non primary replica.
> Also after https://issues.apache.org/jira/browse/IGNITE-16882 was implemented we need to check that the replica is a primary before processing TxFinishReplicaRequest и TxCleanupReplicaRequest.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)