[
https://issues.jboss.org/browse/ISPN-6879?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-6879:
-------------------------------------
I am not certain of the benefit in this case. Even if you go from 100 nodes down to 10,
you would have lost ~90% of your entries and there is no way to know which ones were lost
and which ones were kept.
As long as numOwners < numNodes, I don't see the real benefit as you would have to
throttle the nodes going down to guarantee that data isn't lost. I personally
don't see a user wanting to sit there for minutes just to shut down a subset of nodes.
More than likely they would want to say I want X nodes. Can we not (OpenShift or us) shut
them down in an orderly fashion to do this instead? This seems much safer and wouldn't
have as many user input errors.
Calculate (and expose) minimum number of nodes for data in
Infinispan
---------------------------------------------------------------------
Key: ISPN-6879
URL:
https://issues.jboss.org/browse/ISPN-6879
Project: Infinispan
Issue Type: Feature Request
Components: Cloud Integrations, Server
Reporter: Sebastian Ćaskawiec
Assignee: William Burns
With Kubernetes autoscaling we need to be able to tell what is the minimum amount of
nodes necessary for hosting data (probably some sort of size + number of nodes
estimation).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)