[
https://issues.apache.org/jira/browse/HDFS-12173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108346#comment-16108346
]
Ajay Yadav edited comment on HDFS-12173 at 8/1/17 4:19 PM:
-----------------------------------------------------------
[~daryn], Could you please share more information on this. Since Namenode has
only one stop method does it make sense to update Stop method itself to call
HAState#setState(context, stopState) where stopState obj is set to STOPPING
state?
was (Author: ajayydv):
[~daryn], Could you please share more information on this. Since Namenode has
only one stop method does it make sense to update Stop method itself to call
HAState#setState(context, HAServiceState.STOPPING)?
> MiniDFSCluster cannot reliably use NameNode#stop
> ------------------------------------------------
>
> Key: HDFS-12173
> URL: https://issues.apache.org/jira/browse/HDFS-12173
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.7.0
> Reporter: Daryn Sharp
>
> Sporadic test failures occur because {{NameNode#stop}} used by the mini
> cluster does not properly manage the HA context's state. It directly calls
> {{HAState#exitState(context)}} instead of
> {{HAState#setState(context,state)}}. The latter will properly lock the
> namesystem and update the ha state while locked, while the former does not.
> The result is that while the cluster is stopping, the lock is released and
> any queued rpc calls think the NN is still active and are processed while the
> NN is in an unstable half-stopped state.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
