[ 
https://issues.apache.org/jira/browse/HBASE-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phabricator updated HBASE-4704:
-------------------------------

    Attachment: D117.1.patch

mbautin requested code review of "HBASE-4704 [jira] A JRuby script for 
identifying active master".
Reviewers: Kannan, Liyin, JIRA

  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 adding a one-line hbase-jruby script 
so we can make our jruby scripts proper UNIX executables by including an 
"#!/usr/bin/env hbase-jruby" line at the top.

TEST PLAN
  Run it. Kill the master. Wait for znode to expire. Run again.

REVISION DETAIL
  https://reviews.facebook.net/D117

AFFECTED FILES
  bin/get-active-master.rb
  bin/hbase-jruby

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/249/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> 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
>
>
> 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

        

Reply via email to