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

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/10/20 08:58:00 UTC

[jira] [Updated] (IGNITE-20701) Thin 3.0: Partition awareness uses leader instead of primary replica

     [ https://issues.apache.org/jira/browse/IGNITE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-20701:
------------------------------------
    Description: 
# Problem

* *Partition Leader* and *Primary Partition Replica* can be two different nodes. 
* Primary replica can handle requests more efficiently
* *InternalTableImpl#assignments* is used for client partition awareness, but it returns leaders.

# Action Items

* 

> Thin 3.0: Partition awareness uses leader instead of primary replica
> --------------------------------------------------------------------
>
>                 Key: IGNITE-20701
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20701
>             Project: Ignite
>          Issue Type: Bug
>          Components: thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Critical
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> # Problem
> * *Partition Leader* and *Primary Partition Replica* can be two different nodes. 
> * Primary replica can handle requests more efficiently
> * *InternalTableImpl#assignments* is used for client partition awareness, but it returns leaders.
> # Action Items
> * 



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