Details

      Description

      Currently, you can set capacity-factor to zero on a cache if you don't want a node to own any segment.

      If you want a node to own no data at all, you could set this property on all declared caches. But this wouldn't work for internal caches anyway (locks, counters).

      It would be nice to have a global switch.

      This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster:

      • there would be no data loss
      • the cluster would be back in healthy state faster as no data would be moved around.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                karesti Katia Aresti
                Reporter:
                tsegismont Thomas Segismont
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: