Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 16 May 2013 22:11:16 +0000 (UTC)
From: "Jerry He (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12648063.1368742185247.335487.1368742276222@arcas>
In-Reply-To: <JIRA.12648063.1368742185247@arcas>
References: <JIRA.12648063.1368742185247@arcas>
Subject: [jira] [Created] (HBASE-8565) stop-hbase.sh clean up: backup master
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jerry He created HBASE-8565:
-------------------------------

             Summary: stop-hbase.sh clean up: backup master
                 Key: HBASE-8565
                 URL: https://issues.apache.org/jira/browse/HBASE-8565
             Project: HBase
          Issue Type: Bug
            Reporter: Jerry He
            Priority: Minor


In stop-hbase.sh:
{code}
  # TODO: store backup masters in ZooKeeper and have the primary send them a shutdown message
  # stop any backup masters
  "$bin"/hbase-daemons.sh --config "${HBASE_CONF_DIR}" \
    --hosts "${HBASE_BACKUP_MASTERS}" stop master-backup
{code}

After HBASE-5213, stop-hbase.sh -> hbase master stop will bring up the backup master too via the cluster status znode.

We should not need the above code anymore.

Another issue happens when the current master died and the backup master became the active master.
{code}
nohup nice -n ${HBASE_NICENESS:-0} "$HBASE_HOME"/bin/hbase \
   --config "${HBASE_CONF_DIR}" \
   master stop "$@" > "$logout" 2>&1 < /dev/null &

waitForProcessEnd `cat $pid` 'stop-master-command'
{code}
We can still issue 'hbase-stop.sh' from the old master.
stop-hbase.sh -> hbase master stop -> look for active master -> request shutdown
This process still works.
But the waitForProcessEnd statement will not work since the local master pid is not relevant anymore.
What is the best way in the this case?


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira