You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2025/10/20 06:26:02 UTC

[jira] [Updated] (IGNITE-23025) Java thin 3.0: Use all replicas for partition awareness

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

Evgeny Stanilovsky updated IGNITE-23025:
----------------------------------------
    Fix Version/s: 3.2
                       (was: 3.1)

> Java thin 3.0: Use all replicas for partition awareness
> -------------------------------------------------------
>
>                 Key: IGNITE-23025
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23025
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>
> Currently, client uses primary replicas for partition awareness:
> * Get primary replica per partition from server (*Map<Partition, Replica>*)
> * Compute target replica from key
> * If a direct connection exists to that replica, use it. Otherwise, use any other connection.
> We can improve performance for certain requests (RO transactions) by using non-primary replicas as well:
> * Get all replicas per partition from server (first = primary) (*Map<Partition, List<Replica>>*)
> * Compute target partition from key
> * Iterate over the list of replicas in original order to find an active direct connection
> In other words, "use primary replica if possible, otherwise use non-primary replica, otherwise use any connection".



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