[
https://issues.apache.org/jira/browse/HDFS-16373?focusedWorklogId=691654&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-691654
]
ASF GitHub Bot logged work on HDFS-16373:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Dec/21 11:23
Start Date: 07/Dec/21 11:23
Worklog Time Spent: 10m
Work Description: ayushtkn commented on a change in pull request #3756:
URL: https://github.com/apache/hadoop/pull/3756#discussion_r763895412
##########
File path:
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestMiniDFSCluster.java
##########
@@ -309,6 +309,14 @@ public void testSetUpFederatedCluster() throws Exception {
DFSUtil.addKeySuffixes(
DFS_NAMENODE_HTTP_ADDRESS_KEY, "ns1", "nn1")));
}
+
+ // Shutdown namenodes individually.
+ cluster.shutdownNameNode(0);
+ cluster.shutdownNameNode(1);
Review comment:
I don't think that will repro the issue, Single restart shall pass only
since all other namenodes are up. May be just one shutdown and the other one
restarting will repro...
But that won't look good. My original use case was from a RBF patch, where I
was restaring the namenodes like this only, so kept the logic same
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 691654)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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: [email protected]
For additional commands, e-mail: [email protected]
