[
https://issues.apache.org/jira/browse/HBASE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13594178#comment-13594178
]
Jeffrey Zhong commented on HBASE-7723:
--------------------------------------
The check in for trunk breaks test case(the check in for 0.94 seems all right):
{code}org.apache.hadoop.hbase.replication.TestReplicationQueueFailover{code}
with error message {code}Waited too much time for queueFailover
replication{code}.
The reason is the we removed the root part of path from splitlogs ZK entries
which breaks the following line in file SplitLogManager
{code}HLogSplitter.finishSplitLogFile(logFile.toString(), conf);{code}
The path is a short version and the log splitted file won't be archived which
cause the replication failover case fail because it waits for the archiving
finish.
I'll submit a patch in JIRA HBASE-7944 with other fixes for test case
TestReplicationQueueFailover.
Thanks,
-Jeffrey
> Remove NameNode 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.95.0, 0.94.6
> Reporter: Kevin Odell
> Assignee: Himanshu Vashishtha
> Fix For: 0.95.0, 0.98.0, 0.94.6
>
> 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-94-v5.patch, HBASE-7723-trunk-v1.patch,
> HBASE-7723-trunk-v2.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
