[
https://issues.apache.org/jira/browse/HBASE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569936#comment-13569936
]
Himanshu Vashishtha commented on HBASE-7723:
--------------------------------------------
bq. currently the only logs split are for the ones present under .logs (the
"active" ones)
Right, I was saying for the sake of what this patch is doing. If the root dir
is not present in the given path, it returns as it is.
bq. This means that the logs can even be somewhere else and not only in the
root dir (e.g. custom tool to apply logs from a backup dir)
Going by the existing use cases, I see all goes under the hbase root directory.
If you want to use some other location in future, then one can use a property
to define it. That is beyond the scope of this jira in my opinion (for example,
HLog creation per RS also uses root dir).
> 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.6
>
> Attachments: 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
