hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3223) Get VersionInfo for Running HBase Process
Date Tue, 28 Dec 2010 19:04:46 GMT

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

Nicolas Spiegelberg commented on HBASE-3223:

@Lars: correct assumption.  The idea is that 'bin/hbase VersionInfo' gives info about the
jar that is resident in the HBase dir, whereas JMX will give you the info about the currently
running HBase process.  I guess you could build a JMX client into VersionInfo to give you
both pieces of information, but I see a couple things problematic with that:

1. you would need to refactor the Hadoop VersionInfo for consistency
2. you would want to have JMX also give you static info for consistency.  That's a little
hacky to accomplish.
3. you run into a little bit of confusion in psuedo-distributed mode, where you have multiple
JMX servers but only one HBase dir.  I guess you do a JMX port scan and query every candidate
you find?

> 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message