hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Himanshu Vashishtha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7723) Remove NN URI from ZK splitlogs.
Date Wed, 06 Feb 2013 22:18:18 GMT

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

Himanshu Vashishtha commented on HBASE-7723:
--------------------------------------------

Yes, with NN HA: 
{code}
<name>hbase.rootdir</name>
  <value>hdfs://cloudone/hbase/92</value>
{code}

with non-HA
{code}
<name>hbase.rootdir</name>
  <value>hdfs://cloudone:1234/hbase/94</value>
{code}

When we change the filesystem, we need to restart the cluster after making changes in the
hbase-site.xml file. 
But, we shouldn't wipe the zk data as part of the upgrade. If the shutdown is not proper,
we may have some splitlog znodes, which currently stores the absolute path. When new configuration
comes in, the old path becomes obsolete. Therefore, this jira tends to change the read behavior
for SplitLog entities for 94 (we may have old znodes written by old master and we need to
support rolling upgrade); and change write+read behavior to avoid writing the NN URI for trunk.

                
> Remove NN URI from ZK splitlogs.
> --------------------------------
>
>                 Key: HBASE-7723
>                 URL: https://issues.apache.org/jira/browse/HBASE-7723
>             Project: HBase
>          Issue Type: Bug
>          Components: hadoop2, master
>    Affects Versions: 0.92.0
>            Reporter: Kevin Odell
>            Assignee: Himanshu Vashishtha
>             Fix For: 0.96.0, 0.94.5
>
>         Attachments: 7723-0.94-minimal.txt, 7723-0.94-simple.txt, HBASE-7723-94.patch,
HBASE-7723-94-v2.patch, HBASE-7723-94-v3.patch, HBASE-7723-94-v4.patch, HBASE-7723-trunk-v1.patch,
HBASE-7723-trunk-v2.patch
>
>
> When moving to HDFS HA or removing HA we end up changing the NN namespace.  This can
cause the HMaster not to start up fully due to trying to split phantom HLogs pointing to the
wrong FS - java.lang.IllegalArgumentException: Wrong FS: error messages.  The HLogs in question
might not even be on HDFS anymore.  You have to go in a manually clear out the ZK splitlogs
directory to get HBase to properly boot up.

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

Mime
View raw message