ctubbsii commented on issue #1777: URL: https://github.com/apache/accumulo/issues/1777#issuecomment-726299011
This is a cluster-startup timing issue only, and depends on how the cluster is started. The monitor is doing the correct behavior today... the master isn't up, so it says it's not up. The monitor is not wrong about that. If we introduce a small delay in the monitor before it starts up, that might be okay... but it should not wait indefinitely for the master to be available initially, because it may never be available. However, by doing so, we risk the monitor failing (or delaying) to report a valid problem when the monitor itself is restarted and the rest of the system is expected to be up. The monitor doesn't know what state the rest of the cluster is in, so it doesn't know if it is starting up alone or along with the rest of the cluster. Since cluster startup is more rare than individual node startup, I'm inclined to just not fix this issue... as it's reporting a valid transient issue. After all, it's not that hard to wait a few seconds and refresh. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
