Thanks, we'll just hold off on moving to buddy replication until the 3.3
release. Total replication works well for us at this point.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4260376#4260376
Reply to the post :
Thanks, Richard, for this thorough report. How are you restarting server B?
Hard kill + restart, or normal shutdown plus restart? If it's a hard kill, have
you edited the AS's JGroups configurations to remove FD_SOCK?
I doubt you have removed FD_SOCK; the above questions are just to remove one
Hi Brian, thanks for getting back to me
anonymous wrote : How are you restarting server B? Hard kill + restart, or
normal shutdown plus restart?
I see the same behavior with either a graceful restart or kill -9.
anonymous wrote : If it's a hard kill, have you edited the AS's JGroups
After some basic testing with 3 nodes, I don't immediately see the same issue.
It seems to do a good job of reorganizing the buddy relationships any time a
3rd node comes online. It typically creates a nice ring where each node only
has one buddy. Sounds like the issue might not exist when
Yes, my line of thinking on FD_SOCK was as you stated. Very much a long shot.
:-)
Thanks for testing with 3 nodes. This afternoon I'm setting up a basic unit
test with two nodes; will report back here.
View the original post :
Richard, this is most definitely a bug.
https://jira.jboss.org/jira/browse/JBCACHE-1549
Thanks again for the thorough report.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4259964#4259964
Reply to the post :
