[
https://issues.apache.org/jira/browse/HBASE-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573755#comment-13573755
]
Himanshu Vashishtha commented on HBASE-7723:
--------------------------------------------
There are two use cases here:
a) Supporting a rolling restart
b) Change in NN URI.
They are mutually exclusive. This jira deals only with b). This requires a
restart of the entire cluster, which is OK. I grepped the above tools, and they
are using "conf" object, which is fine too. The only problem is the zondes
which contains absolute path now become irrelevant because of the URI change.
One needs to manually remove those stale znodes. This patch intends to use
relative path to avoid such behavior.
bq. where we want to get to hdfs where the config may have the single nn format
but we're running the ha nn – or vice versa.
We need a restart in this case, which should serve the purpose. All the nodes
will have right conf property then, right?
For a), we don't need to change anything for this imo.
> 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
