[ 
https://issues.apache.org/jira/browse/HDDS-15737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Doroszlai updated HDDS-15737:
------------------------------------
        Parent:     (was: HDDS-5626)
    Issue Type: Bug  (was: Sub-task)

> Intermittent failure in 
> TestContainerBalancerDatanodeNodeLimit#balancerShouldOnlySelectConfiguredIncludeContainers
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-15737
>                 URL: https://issues.apache.org/jira/browse/HDDS-15737
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: test
>            Reporter: Chi-Hsuan Huang
>            Assignee: Chi-Hsuan Huang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.3.0
>
>
> {noformat}
> java.lang.AssertionError:
> Expecting actual not to be empty
>       at 
> org.apache.hadoop.hdds.scm.container.balancer.TestContainerBalancerDatanodeNodeLimit.balancerShouldOnlySelectConfiguredIncludeContainers\(TestContainerBalancerDatanodeNodeLimit.java:473\)
> {noformat}
> Failed 3 times out of 100 repeated runs of the whole class \(parameterized 
> cluster sizes \[3\], \[7\], \[8\]\) in a flaky\-test\-check run based on 
> master commit 27763e6648: 
> [https://github.com/chihsuan/ozone/actions/runs/28691674922|https://github.com/chihsuan/ozone/actions/runs/28691674922]
> The test was added in HDDS-14618. It configures include containers "1, 4, 5" 
> and asserts that getContainerToSourceMap\(\) is not empty, but the mocked 
> cluster layout is generated with ThreadLocalRandom \(TestableCluster\), so 
> occasionally none of the included containers is eligible for a move. Same 
> family as HDDS\-11093 and HDDS\-11855.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to