[jboss-jira] [JBoss JIRA] (WFLY-6064) Distributed SFSB cache entries may rehash to different nodes following topology change
Radoslav Husar (JIRA)
issues at jboss.org
Tue Feb 2 11:27:00 EST 2016
[ https://issues.jboss.org/browse/WFLY-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157825#comment-13157825 ]
Radoslav Husar commented on WFLY-6064:
--------------------------------------
Tangent failure in CI:
http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87591&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments
https://gist.github.com/rhusar/380c8ecb0a03d1284f86
> Distributed SFSB cache entries may rehash to different nodes following topology change
> --------------------------------------------------------------------------------------
>
> Key: WFLY-6064
> URL: https://issues.jboss.org/browse/WFLY-6064
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> A distributed SFSB is stored in 2 cache entries, one mapping the bean ID to a serialization group ID, and another mapping the group ID to a map of bean instances.
> We ensure that both cache entries will hash to the local node, but following a topology change, these entries could get re-mapped to different nodes.
> If we made the group ID = the bean Id of the first bean in the group, this solves the problem for 90% of use cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list