[infinispan-issues] [JBoss JIRA] (ISPN-3223) HotRod 2.0 Client recieves stale toplogy view on instance leave
[
https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-3223:
----------------------------------------
Alan, although I see the same log messages, the logic works fine because even though
there's two members in the cluster membership, the consistent hash points everything
towards the only running node, even though the keys vary, so it's not the same case as
Takayoshi has. Creating a new JIRA to track your particular issue.
HotRod 2.0 Client recieves stale toplogy view on instance leave
---------------------------------------------------------------
Key: ISPN-3223
URL: https://issues.jboss.org/browse/ISPN-3223
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 5.2.4.Final, 5.3.0.CR1, 7.0.0.Beta1
Reporter: Takayoshi Kimura
Assignee: Galder Zamarreño
Fix For: 7.0.0.Beta2, 7.0.0.Final
Attachments: hr-protocol-13.log, hr-protocol-20.log
When killed a HotRod server node, HotRod Clinet sometimes recieves a stale toplogy view
which includes the dead node and uses it as a latest view. In this case the client keeps
trying to connect that node and keeps failing.
Looks like the AbstractEncoder1x.generateTopologyResponse() takes care of node join but
doesn't handle node leave:
{noformat}
if (!serverEndpointsMap.keySet.containsAll(cacheMembers)) {
{noformat}
For example, serverEndpointsMap.keySet is [A, B, C] and the actual cacheMembers is [A,
B].
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)