[
https://issues.redhat.com/browse/ISPN-9699?page=com.atlassian.jira.plugin...
]
Pedro Zapata Fernandez updated ISPN-9699:
-----------------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid
Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint
#35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39
(was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint
#31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35,
DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38)
Cluster member owning no data
-----------------------------
Key: ISPN-9699
URL:
https://issues.redhat.com/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: 9.4.7.Final, 10.0.0.Beta1
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.13.8#713008)