Hi all, In my company we are developing a visual tool for Bookkeeper Management and we would like to have more information about the status of a Bookie just by using RPC calls. We already have getBookieInfo that is only reporting about disk space usage.
Examples of useful info: - link to metrics endpoint - last minor/major gc execution timestamp - last jvm start timestamp (uptime) - configuration file We already have the http endpoint but it comes with several disadvantages: - it is a secondary channel (so you have to use two channels to talk to the bookie) - there is no way of getting the http address, as it is not advertised on metadata discovery service - it does not support security (auth/tls..) yet Given that I am mostly using Kerberos, going to the http way will need separate security configurations: for bookie RPC and for HTTP. So that's why I would prefer to use the standard binary RPC protocol: only one client, only one auth, security is already ok, no additional discovery info. If you guys agree on the approach we can send a patch that includes the support for publishing more information on that RPC Cheers Enrico
