You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Phabricator (Updated) (JIRA)" <ji...@apache.org> on 2011/11/11 10:28:53 UTC
[jira] [Updated] (HBASE-4704) A JRuby script for identifying active
master
[ https://issues.apache.org/jira/browse/HBASE-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phabricator updated HBASE-4704:
-------------------------------
Attachment: HBASE-4704.D117.2.patch
mbautin updated the revision "HBASE-4704 [jira] A JRuby script for identifying active master".
Reviewers: Kannan, Liyin, JIRA
Fixing the script to actually work on trunk. Tested on a dev cluster, killed the master, tested again, got "Master not running" after znode expiration. Hacked the script to use incorrect ZK port, got a ZK exception and a nonzero error code, as expected.
REVISION DETAIL
https://reviews.facebook.net/D117
AFFECTED FILES
bin/get-active-master.rb
bin/hbase-jruby
> A JRuby script for identifying active master
> --------------------------------------------
>
> Key: HBASE-4704
> URL: https://issues.apache.org/jira/browse/HBASE-4704
> Project: HBase
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Assignee: Mikhail Bautin
> Priority: Trivial
> Fix For: 0.94.0
>
> Attachments: D117.1.patch, HBASE-4704.D117.2.patch
>
>
> This simple script reads the HBase master ZK node and outputs the hostname of the active master. This is needed so that operational scripts can decide where the primary master is running. I am also including a one-line hbase-jruby script so we can make our jruby scripts proper UNIX executables by including an "#!/usr/bin/env hbase-jruby" at the top.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira