[infinispan-issues] [JBoss JIRA] Updated: (ISPN-434) Creating a new distributed cache on a non-coordinator node causes rehashing to hang
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Mon May 17 10:11:06 EDT 2010
[ https://jira.jboss.org/browse/ISPN-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-434:
-------------------------------
Fix Version/s: 5.1.0.BETA1
5.1.0.Final
(was: 4.1.0.Final)
(was: 4.1.0.CR1)
Priority: Minor (was: Major)
Steps to Reproduce:
1. C1 (coord) starts replicated cache
2. C2 starts replicated cache
3. C2 starts distributed cache
4. C1 starts distributed cache
Step 3 will hang until step 4 completes. So unless these happen in different threads - on different servers - this rehash will hang.
Downgrading the priority on this since it is only a problem when you have a local thread starting nodes in the same VM. A very artificial case, which really only applies to unit tests. See workaround for details.
> Creating a new distributed cache on a non-coordinator node causes rehashing to hang
> -----------------------------------------------------------------------------------
>
> Key: ISPN-434
> URL: https://jira.jboss.org/browse/ISPN-434
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Affects Versions: 4.1.0.ALPHA3
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Priority: Minor
> Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> If a cluster is already formed (perhaps due to another cache instance being started, such as a replicated one) and subsequently a distributed cache is created and started, first on a non-coordinator node, the startup sequence will hang until the cache is also started on the coordinator.
> E.g.,
> 1. C1 (coord) starts replicated cache
> 2. C2 starts replicated cache
> 3. C2 starts distributed cache
> 4. C1 starts distributed cache
> Step 3 will hang until step 4 completes. So unless these happen in different threads - on different servers - this rehash will hang.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list