ddanielr commented on issue #3159: URL: https://github.com/apache/accumulo/issues/3159#issuecomment-1382615644
@cshannon The max timeout behavior you suggested makes sense, but I'm cautious about inversely changing the behavior of a property. The is the current definition of the property behavior. https://github.com/apache/accumulo/blob/fbe1ee8cfc98f788329208419d682429c90784c2/core/src/main/java/org/apache/accumulo/core/conf/Property.java#L346-L349 Would it make sense to have two sets of these properties? One for the critical path, the other as a churn/balancing safeguard for startup? The timeout logic you are suggesting could be rolled into the new "critical" property and we wouldn't flip existing/expected property behavior. If not reached, startup will be terminated (timeout). `manager.startup.tserver.critical.min.count` `manager.startup.tserver.critical.timeout` if not reached, startup will be delayed, not terminated (wait time). `manager.startup.tserver.avail.min.count` `master.startup.tserver.avail.max.wait=5min` -- 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]
