[
https://issues.apache.org/jira/browse/IGNITE-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379903#comment-16379903
]
Vyacheslav Daradur commented on IGNITE-5357:
--------------------------------------------
[~ascherbakov], please have a look at the prepared PR:
[https://github.com/apache/ignite/pull/3578/files]
[Ci.tests of
PR|https://ci.ignite.apache.org/viewLog.html?buildId=1113498&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
look the same as [the master
branch|https://ci.ignite.apache.org/viewLog.html?buildId=1113404&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll].
Should we add any special test cases for this change, I think it's covered by
existing tests?
> 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)
