[jira] [Updated] (HDFS-16373) Fix MiniDFSCluster restart in case of multiple namenodes
[ https://issues.apache.org/jira/browse/HDFS-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shilun Fan updated HDFS-16373: -- Component/s: test Hadoop Flags: Reviewed Target Version/s: 3.2.4, 3.3.2, 3.4.0 Affects Version/s: 3.2.4 3.3.2 3.4.0 > Fix MiniDFSCluster restart in case of multiple namenodes > > > Key: HDFS-16373 > URL: https://issues.apache.org/jira/browse/HDFS-16373 > Project: Hadoop HDFS > Issue Type: Bug > Components: test >Affects Versions: 3.4.0, 3.3.2, 3.2.4 >Reporter: Ayush Saxena >Assignee: Ayush Saxena >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.3.2, 3.2.4 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > In case of multiple namenodes, if more than one namenode are restarted, it > fails. Since the restartNamenode checks for all the namenodes to get up, But > if 2 namenodes are down, and we restart one, the other namenode won't be up, > so restart fails. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-16373) Fix MiniDFSCluster restart in case of multiple namenodes
[ https://issues.apache.org/jira/browse/HDFS-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Sun updated HDFS-16373: Fix Version/s: 3.3.2 (was: 3.3.3) > Fix MiniDFSCluster restart in case of multiple namenodes > > > Key: HDFS-16373 > URL: https://issues.apache.org/jira/browse/HDFS-16373 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Ayush Saxena >Assignee: Ayush Saxena >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.3.2, 3.2.4 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > In case of multiple namenodes, if more than one namenode are restarted, it > fails. Since the restartNamenode checks for all the namenodes to get up, But > if 2 namenodes are down, and we restart one, the other namenode won't be up, > so restart fails. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-16373) Fix MiniDFSCluster restart in case of multiple namenodes
[ https://issues.apache.org/jira/browse/HDFS-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDFS-16373: -- Labels: pull-request-available (was: ) > Fix MiniDFSCluster restart in case of multiple namenodes > > > Key: HDFS-16373 > URL: https://issues.apache.org/jira/browse/HDFS-16373 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Ayush Saxena >Assignee: Ayush Saxena >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > In case of multiple namenodes, if more than one namenode are restarted, it > fails. Since the restartNamenode checks for all the namenodes to get up, But > if 2 namenodes are down, and we restart one, the other namenode won't be up, > so restart fails. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
