[
https://issues.apache.org/jira/browse/IGNITE-23025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-23025:
------------------------------------
Description:
Currently, client uses primary replicas for partition awareness:
* Get primary replicas per partition from server
* 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)
* 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".
> 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.0.0-beta2
>
>
> Currently, client uses primary replicas for partition awareness:
> * Get primary replicas per partition from server
> * 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)
> * 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)
