Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0.4, 1.1.1, 2.0.2-alpha
-
None
-
Reviewed
Description
When I manually ran TestBalancerWithNodeGroup, it always timed out in my machine. Looking at the Jerkins report build #3573, TestBalancerWithNodeGroup somehow was skipped so that the problem was not detected.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-6621 Hadoop Balancer prematurely exits iterations
- Closed
- duplicates
-
HDFS-4365 Add junit timeout to TestBalancerWithNodeGroup
- Resolved
- is depended upon by
-
HDFS-4386 Backport HDFS-4261 to branch-1 to fix timeout in TestBalancerWithNodeGroup
- Resolved
- is duplicated by
-
HDFS-5706 Should reset Balancer.Parameters.DEFALUT.policy in TestBalancer
- Resolved
- is related to
-
HDFS-4365 Add junit timeout to TestBalancerWithNodeGroup
- Resolved
- is required by
-
HDFS-4275 MiniDFSCluster-based tests fail on Windows due to failure to delete test namenode directory
- Resolved
-
HDFS-4289 FsDatasetImpl#updateReplicaUnderRecovery throws errors validating replica byte count on Windows
- Resolved
- relates to
-
HDFS-4376 Fix several race conditions in Balancer and resolve intermittent timeout of TestBalancerWithNodeGroup
- Closed
-
HDFS-4382 Fix typo MAX_NOT_CHANGED_INTERATIONS
- Closed