Closed onsi closed 9 years ago
@fraenkel said: I am leery of another state since its not really a state of the LRP but of the Cell. There is no knowledge as to why it failed or when it would recover other than retry. Whether its full or just some network failure, its really no different. Yes, we can do better at retries if we knew it was a placement issue, but you still don't know when its safe to retry.
@onsi replied: It's not even the state of "the Cell" but really the state of "the Cluster". I agree that adding yet another state to the LRP is sucky.
I'd go back to what we need. If the cluster is full we need:
UNCLAIMED
state. The converger will retry every 30s (which should be OK)FAILED
state (or maybe better would be UNALLOCATABLE
or UNCLAIMABLE
which behaves just like UNCLAIMED
but signals to the consumer that the cluster is full).Will open an Issue with all this in it and perhaps we can discuss. Not updating the doc just yet.
Killing the FAILED
state idea -- I've submitted #15 as a proposal for how to communicate at-capacity situations back to the user.
The doc considers this a TBD. Let's figure it out.