You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nicolas Spiegelberg (JIRA)" <ji...@apache.org> on 2010/11/04 22:04:40 UTC
[jira] Assigned: (HBASE-2932) Allow Per-Process SVN Version
Information
[ https://issues.apache.org/jira/browse/HBASE-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Spiegelberg reassigned HBASE-2932:
------------------------------------------
Assignee: (was: Nicolas Spiegelberg)
unassigning in case a new developer wants to work on this as a warmup-task.
> 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
> Priority: Minor
>
> 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.