How to handle a JDG cluster with only a few nodes where caches enable partition handling ?
Issue
- A cache become
DEGRADED_MODEif one of two nodes goes down, if a new node is started the cache is not going back toAVAILABLE. Is this a bug or how can this solved? - There is a different behavior if a node of a two node cluster is shutting down, sometimes the remaining node stays
AVAILABLEsoemtimesDEGRADED_MODE. What is the reason for this? - If one node is left in a cluster I see the message below and new nodes are not able to join
WARN [org.infinispan.CLUSTER] (transport-thread--p4-t23) [Context=default]ISPN000320: After merge (or coordinator change), cache still hasn't recovered a majority of members and must stay in degraded mode. Current members are [node2], lost members are [node1], stable members are [node1, node2]
Environment
- Red Hat JBoss Data Grid (JDG)
- 6.x
- 7.0, 7.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
