[jira] [Commented] (HBASE-26296) Make it easier to orchestrate rolling upgrades

["Bryan Beaudreault (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-26296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419941#comment-17419941 ] 

Bryan Beaudreault commented on HBASE-26296:
-------------------------------------------

I realized that RegionServer versions are available via getClusterMetrics().getLiveServerMetrics(). Each ServerMetrics has a getVersion().

However, we still have no way to get the version for backup masters.

> Make it easier to orchestrate rolling upgrades
> ----------------------------------------------
>
>                 Key: HBASE-26296
>                 URL: https://issues.apache.org/jira/browse/HBASE-26296
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Bryan Beaudreault
>            Priority: Minor
>
> In order to orchestrate rolling upgrades, we need a way to query VersionInfo on a per-server basis. Currently I can see version exposed in two ways:
>  * One can hit the /dump endpoint, but this creates a ton of extra output and is not machine parseable.
>  * One can call Admin.getClusterMetrics() with Option.HBASE_VERSION, but the resulting response only has a single getHBaseVersion() which only represents the version for the active HMaster
> We could make it a lot easier to orchestrate rolling upgrades if we exposed the VersionInfo details for all servers in the cluster. At a minimum I think we could add it to the /jmx response, but it would also be very helpful to add it to Admin.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)