hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12173) MiniDFSCluster cannot reliably use NameNode#stop
Date Tue, 01 Aug 2017 03:56:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108346#comment-16108346

Ajay Yadav commented on HDFS-12173:

 [~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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message