[
https://issues.apache.org/jira/browse/HBASE-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Spiegelberg updated HBASE-2932:
---------------------------------------
Priority: Major (was: Minor)
We had some internal discussion about this today. Andrew Ryan suggested that
we export this via JMX. +1 If we go the JMX route, we can expose VersionInfo
via RegionServerMetrics/MasterMetrics and quickly fix this for both Hadoop &
HBase. Raising priority to Major because we're hitting this a lot more now
that we allow rolling upgrades and a corps internal Hadoop release cycle may
not necessarily be correlated to the HBase release cycle.
> Allow Per-Process SVN Version Information
> -----------------------------------------
>
> Key: HBASE-2932
> URL: https://issues.apache.org/jira/browse/HBASE-2932
> Project: HBase
> Issue Type: Improvement
> Components: ipc, master, regionserver, scripts
> Reporter: Nicolas Spiegelberg
>
> Currently, we can use bin/hbase VersionInfo to get jar svn version
> information, but that is not necessarily the jar of the currently-running
> process. HBase.getClusterStatus() contains SVN info for the running primary
> HMaster process. We need to add a way to get SVN version information for
> online RegionServers (more important) & Backup HMasters (not so important).
> With the addition of rolling upgrades, we are more likely to get into a
> situation where part of the RS in our cluster is on a different version. If
> we start seeing problems during rolling, it would be nice to know if this
> might be a versioning problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
