[
https://issues.apache.org/jira/browse/HBASE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573144#comment-13573144
]
stack commented on HBASE-7723:
------------------------------
The difference is port number only? (that 0.92 vs 0.94 is a clouderia-ism? Or
you are thinking log splitting should just work even if hbase.rootdir is
relatively shifted?) HA NN has no 'port' number? Can't we equate these
'filesystems'? They are the 'same', no? Its just that one has a NN ensemble
serving its metadata?
Its probably fine making log paths relative to root dir so you can move the
root dir and it would still work (Hopefully the case where the zk data from one
filesystem is set against a different filesystem will just fail horribly).
> 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-94-v5.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
