[
https://issues.apache.org/jira/browse/IGNITE-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379552#comment-16379552
]
ASF GitHub Bot commented on IGNITE-5357:
----------------------------------------
GitHub user DALukjanenko opened a pull request:
https://github.com/apache/ignite/pull/3581
IGNITE-5357 replicated cache reads load balancing was added
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DALukjanenko/ignite IGNITE-5357.master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3581.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3581
----
commit 5cc0906838f4916060149a62b51d6904f63a11a7
Author: Dmitry Lukjanenko <lukdiman.developer@...>
Date: 2018-02-28T00:14:36Z
IGNITE-5357 replicated cache reads load balancing was added
----
> Replicated cache reads load balancing.
> --------------------------------------
>
> Key: IGNITE-5357
> URL: https://issues.apache.org/jira/browse/IGNITE-5357
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.6
> Reporter: Alexei Scherbakov
> Assignee: Lukjanenko Dmitry
> Priority: Major
> Labels: newbie
> Fix For: 2.5
>
>
> Currently all read requests from client node to replicated cache will go
> through primary node for key.
> Need to select random affinity node in topology and send request here (only
> if readFromBackups=true)
> If where are server nodes collocated on same host with client, must select
> target node from them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
