Bug 1179926 - PartitionHandling: remove unavailable mode
Summary: PartitionHandling: remove unavailable mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: 6.4.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: jdg64-GA-Blockers
TreeView+ depends on / blocked
 
Reported: 2015-01-07 20:06 UTC by Dan Berindei
Modified: 2015-01-28 13:29 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5060 0 Critical Coding In Progress PartitionHandling: remove unavailable mode 2015-01-07 20:06:29 UTC

Description Dan Berindei 2015-01-07 20:06:28 UTC
The Unavailable mode name is misleading, because some keys are available, just like in Degraded mode.

The only difference between Degraded and Unavailable is that with Degraded the cluster might recover without manual intervention. The administrator still has to know a lot more details in order to decide whether manual intervention is needed or not. So it would be less confusing if gracefully shutting down numOwners nodes in quick succession would leave the cache in Degraded mode instead of Unavailable.

Instead of removing the Unavailable mode completely, we could also change it to deny access to all the keys and allow the administrator to use it. E.g. if we had an operation to dump the cache into a shared store and another to load the cache from a shared store, the administrator could force the cache into Unavailable mode while dumping/loading the cache.

Comment 2 Dan Berindei 2015-01-12 10:45:17 UTC
PR: https://github.com/infinispan/jdg/pull/436


Note You need to log in before you can comment on or make changes to this bug.