[infinispan-issues] [JBoss JIRA] (ISPN-2738) Joining node ignored by hotrod clients in REPL clustering mode
Dan Berindei (JIRA)
jira-events at lists.jboss.org
Wed Jan 23 07:04:47 EST 2013
[ https://issues.jboss.org/browse/ISPN-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749861#comment-12749861 ]
Dan Berindei commented on ISPN-2738:
------------------------------------
In my fix for ISPN-2632 I replaced the interceptor with a check to not send the topology update unless all the consistent hash members also exist in the address cache. Unfortunately I only added the check for distributed caches (see AbstraceEncoder1x/AbstractTopologyAwareEncoder1x.writeHashTopologyHeader).
The fix is to add the same check on all the code paths that write a topology update.
> Joining node ignored by hotrod clients in REPL clustering mode
> --------------------------------------------------------------
>
> Key: ISPN-2738
> URL: https://issues.jboss.org/browse/ISPN-2738
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.CR2
> Reporter: Michal Linhard
> Assignee: Dan Berindei
> Priority: Blocker
> Fix For: 5.2.0.Final
>
>
> resilience 4-3-4 REPL mode for JDG 6.1.0.ER9 (infinispan 5.2.0.CR2):
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/job/edg-60-resilience-repl-4-3/31/artifact/report/stats-throughput.png
> after rejoin of killed node the load is not redistributed to all three nodes again
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list