[infinispan-issues] [JBoss JIRA] (ISPN-9699) Cluster member owning no data

[Radoslav Husar (Jira)]

     [ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated ISPN-9699:
---------------------------------
    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.


  was:
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 cached. 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.




> Cluster member owning no data
> -----------------------------
>
>                 Key: ISPN-9699
>                 URL: https://issues.jboss.org/browse/ISPN-9699
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 9.4.1.Final
>            Reporter: Thomas Segismont
>            Assignee: Katia Aresti
>            Priority: Major
>             Fix For: 10.0.0.Alpha2, 9.4.3.Final
>
>
> 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.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)