ctubbsii commented on pull request #2020: URL: https://github.com/apache/accumulo/pull/2020#issuecomment-819676434
> Why? That information is useful in certain situations - especially if you have zk node failures or need to do a zk node restart. The reasoning seems discussed on the referenced issue. The underlying issue is that our ability to display this is dependent on an insecure and outdated way of retrieving information from the ZK servers (4LW) that have been replaced by a new way (Adminserver) and is broken by default, without significant extra work to support retrieving the information from ZK under a variety of circumstances (such as when TLS is enabled for the Adminserver). As hinted at on the issue, but perhaps not explicitly stated, it's better to remove the responsibility of displaying ZK stats from Accumulo and let users monitor their own ZK instances their own way, via features provided by ZK, rather than us. The Accumulo monitor should not be responsible for monitoring other services in a user's cluster, but should be narrowly scoped to monitor Accumulo itself, leaving the responsibility of monitoring other services in a user's cluster to those other projects or to users. Even if the information is useful, it's not reasonable to consider the monitoring of other services in a user's cluster to be in scope for Accumulo, especially as the amount of code required to support it grows (to handle 4LW and Adminserver, with and without TLS, etc.) -- 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]
