[
https://issues.apache.org/jira/browse/HBASE-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3940:
-------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Applied to TRUNK. Nice one Li.
> HBase daemons should log version info at startup and possibly periodically
> --------------------------------------------------------------------------
>
> Key: HBASE-3940
> URL: https://issues.apache.org/jira/browse/HBASE-3940
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.92.0
> Reporter: Todd Lipcon
> Assignee: Li Pi
> Priority: Blocker
> Labels: noob
> Fix For: 0.92.0
>
> Attachments: hbase-3940.diff
>
>
> As someone who deals with different clusters running different versions
> (sometimes pre-releases), I often end up with an error log but not great info
> as the exact revision the log came from. This is even more tricky with things
> like rolling update.
> To help with this, the RS and Master should log their complete version string
> at startup. Potentially, they could also log it once every 12 hours as well,
> so that even with log rotation we can tell the current version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
