ddanielr commented on issue #3159: URL: https://github.com/apache/accumulo/issues/3159#issuecomment-1386345190
I agree with @cshannon that the halting behavior is a valid desire, just not for the original properties. A kubernetes deployment of accumulo would benefit from having the "critical.min.count" and "wait and fail" behavior properties available to use for defining startup and readiness probes. @EdColeman I don't see this as making any decisions about cluster management since these properties are all optional. If we were to set them to required values then I could see that being a decision and carrying backlash. --- Based on the discussion so far, it sounds like fixing the original timeout logic to be "Wait and Continue" is the correct move. Adding a second set of properties for "critical.min.count" and "wait and fail" behavior is a valid requirement and makes sense to add. However, that work should be completed in a separate ticket. If that sounds good, I'll work on this timeout fix and make the additional ticket for implementing the second optional property set. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
