[
https://issues.jboss.org/browse/ISPN-8976?page=com.atlassian.jira.plugin....
]
Ryan Emerson commented on ISPN-8976:
------------------------------------
[~robertcernak] If you do not need Conflict Resolution on partition merge then I suggest
that you configure your cache to use MergePolicy.NONE and the CR phase, which appears to
be causing the problem, will be skipped.
My intention is to fix this issue, ideally in time for 9.3.0.Final but I cannot guarantee
this due to other commitments etc.
2 subclusters failed to merge to 1 cluster -
IllegalLifecycleStateException
---------------------------------------------------------------------------
Key: ISPN-8976
URL:
https://issues.jboss.org/browse/ISPN-8976
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.1.4.Final
Reporter: Robert Cernak
Assignee: Ryan Emerson
Attachments: logs.zip
At the beginning I have main cluster consisted of 8 nodes.
Then I disconnected main switch on which these nodes were connected.
This leaded to separating main cluster to 2 subclusters - first with 2 nodes and second
with 6 nodes. This was expected.
After that I rebooted the nodes. After reboot, nodes again correctly formed 2 subclusters
with 2 and 6 members.
After a long time when all nodes were stable with low cpu load, I connected the main
switch back which should lead to recreation of main cluster with 8 controllers.
However main cluster did not recovered:
subcluster2 did not change - still had 6 nodes connected - no new members
subcluster1 - nodes did not connect with subcluster2 and after cca 30min they left the
cluster.
When I checked infinispan logs of node1 from 1st subcluster I had
IllegalLifecycleStateException for every created cache (see included logs.zip):
[transport-thread-744a974a-2811-4f79-ac63-f32daf005d7f-p4-t6]
(ClusterCacheStatus.java:599) - ISPN000228: Failed to recover cache XXX state after the
current node became the coordinator
org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and
cannot be reused. Recreate the cache container.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)