[jira] [Updated] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up
[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-6853: - Labels: (was: BB2015-05-TBR) > MiniDFSCluster.isClusterUp() should not check if null NameNodes are up > -- > > Key: HDFS-6853 > URL: https://issues.apache.org/jira/browse/HDFS-6853 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: James Thomas >Assignee: James Thomas > Attachments: HDFS-6853.2.patch, HDFS-6853.patch > > > Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). > When we try to restart the other NN (NN1), we wait for isClusterUp() to > return true, but this will never happen because NN0 is null and isNameNodeUp > returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up
[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HDFS-6853: - Target Version/s: (was: 2.8.0) > MiniDFSCluster.isClusterUp() should not check if null NameNodes are up > -- > > Key: HDFS-6853 > URL: https://issues.apache.org/jira/browse/HDFS-6853 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: James Thomas >Assignee: James Thomas > Attachments: HDFS-6853.2.patch, HDFS-6853.patch > > > Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). > When we try to restart the other NN (NN1), we wait for isClusterUp() to > return true, but this will never happen because NN0 is null and isNameNodeUp > returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up
[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated HDFS-6853: --- Labels: BB2015-05-TBR (was: ) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up -- Key: HDFS-6853 URL: https://issues.apache.org/jira/browse/HDFS-6853 Project: Hadoop HDFS Issue Type: Bug Reporter: James Thomas Assignee: James Thomas Labels: BB2015-05-TBR Attachments: HDFS-6853.2.patch, HDFS-6853.patch Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). When we try to restart the other NN (NN1), we wait for isClusterUp() to return true, but this will never happen because NN0 is null and isNameNodeUp returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up
[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Thomas updated HDFS-6853: --- Attachment: HDFS-6853.2.patch Reposted same patch to retrigger Jenkins. MiniDFSCluster.isClusterUp() should not check if null NameNodes are up -- Key: HDFS-6853 URL: https://issues.apache.org/jira/browse/HDFS-6853 Project: Hadoop HDFS Issue Type: Bug Reporter: James Thomas Assignee: James Thomas Attachments: HDFS-6853.2.patch, HDFS-6853.patch Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). When we try to restart the other NN (NN1), we wait for isClusterUp() to return true, but this will never happen because NN0 is null and isNameNodeUp returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up
[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Thomas updated HDFS-6853: --- Attachment: HDFS-6853.patch MiniDFSCluster.isClusterUp() should not check if null NameNodes are up -- Key: HDFS-6853 URL: https://issues.apache.org/jira/browse/HDFS-6853 Project: Hadoop HDFS Issue Type: Bug Reporter: James Thomas Attachments: HDFS-6853.patch Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). When we try to restart the other NN (NN1), we wait for isClusterUp() to return true, but this will never happen because NN0 is null and isNameNodeUp returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HDFS-6853) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up
[ https://issues.apache.org/jira/browse/HDFS-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Thomas updated HDFS-6853: --- Assignee: James Thomas Status: Patch Available (was: Open) MiniDFSCluster.isClusterUp() should not check if null NameNodes are up -- Key: HDFS-6853 URL: https://issues.apache.org/jira/browse/HDFS-6853 Project: Hadoop HDFS Issue Type: Bug Reporter: James Thomas Assignee: James Thomas Attachments: HDFS-6853.patch Suppose we have a two-NN cluster and then shut down one of the NN's (NN0). When we try to restart the other NN (NN1), we wait for isClusterUp() to return true, but this will never happen because NN0 is null and isNameNodeUp returns false for a null NN. -- This message was sent by Atlassian JIRA (v6.2#6252)
