Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5060

PartitionHandling: remove unavailable mode

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Critical Critical
    • 7.1.0.Beta1, 7.1.0.Final
    • 7.0.2.Final, 7.1.0.Alpha1
    • Core
    • None

      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.

              dberinde@redhat.com Dan Berindei (Inactive)
              dberinde@redhat.com Dan Berindei (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: