[
https://issues.apache.org/jira/browse/HBASE-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975936#action_12975936
]
Nicolas Spiegelberg commented on HBASE-3223:
--------------------------------------------
I agree with the idea that you need easy setup & access to information. I
think, however, that people will mainly care about the running process version
when they actually have a cluster up, working, and being upgraded to fix
perceived shortcomings in the system. If you have a working cluster and you
don't already have some monitoring tools setup (hopefully, with some tool that
can read JMX), God help that admin. He needs more visibility than just the
version number.
> Get VersionInfo for Running HBase Process
> -----------------------------------------
>
> Key: HBASE-3223
> URL: https://issues.apache.org/jira/browse/HBASE-3223
> Project: HBase
> Issue Type: Improvement
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
> Fix For: 0.90.1
>
> Attachments: HBASE-3223-fix.patch
>
>
> bin/hbase VersionInfo is a great existing utility to provide version info
> about Hbase jar files. Unfortunately, there is no way to currently get this
> information for the running process. For this jira, add an easy/quick way to
> see verify the rev of the running jar.
> We got recently bit internally because our running jar was a different
> version from the jar that we had recently pushed and caused havoc on our
> cluster. This problem is more important to fix now that we have rolling
> upgrades and will regularly have cluster scenarios with mixed-version RSs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
