hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7824) Improve master start up time when there is log split work
Date Sat, 23 Feb 2013 05:30:14 GMT

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

stack commented on HBASE-7824:

Patch looks great.

Why we doing the below?  Doesn't recoverablezookeeper do this for us?

-      LOG.error("ZooKeeper exception trying to set cluster as down in ZK", e);
+      if (e instanceof KeeperException.SessionExpiredException) {
+        LOG.warn("ZK session expired. Retry a new connection...");
+        try {
+          this.zooKeeper.reconnectAfterExpiration();
+          this.clusterStatusTracker.setClusterDown();

+1 on commit.
> Improve master start up time when there is log split work
> ---------------------------------------------------------
>                 Key: HBASE-7824
>                 URL: https://issues.apache.org/jira/browse/HBASE-7824
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>             Fix For: 0.94.6
>         Attachments: hbase-7824.patch, hbase-7824_v2.patch
> When there is log split work going on, master start up waits till all log split work
completes even though the log split has nothing to do with meta region servers.
> It's a bad behavior considering a master node can run when log split is happening while
its start up is blocking by log split work. 
> Since master is kind of single point of failure, we should start it ASAP.

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

View raw message