[ 
https://issues.apache.org/jira/browse/HDDS-10612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833866#comment-17833866
 ] 

Anastasia Filippova commented on HDDS-10612:
--------------------------------------------

[~ivanandika] Thanks!

I also saw the root cause, but I can't figure out why this container 3 went 
into closed state. We saw this container in an open state and after that we try 
to close it only once. I don’t understand the reason why he decided to close 
himself.

Yes, we can call the “ozone admin container list” only once, but this will not 
solve our problem, since we can still get into a situation where the container 
in the list will be in the open state, and when we try to close the container, 
it will already be in the closing state .

Now I’m trying to understand the reason for closing the container and looking 
at how best to fix the test so that this doesn’t happen again.

> Add Robot test to verify Container Balancer for RATIS containers
> ----------------------------------------------------------------
>
>                 Key: HDDS-10612
>                 URL: https://issues.apache.org/jira/browse/HDDS-10612
>             Project: Apache Ozone
>          Issue Type: Test
>          Components: test
>            Reporter: Anastasia Filippova
>            Assignee: Anastasia Filippova
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>
> Currently there are only unit tests for Container Balancer and no acceptance 
> tests at all. At a minimum, we should add a Robot test to verify Container 
> Balancer for RATIS containers. And probably in the future we should add robot 
> test for EC case.
> Test case:
> 1. Move 1 datanode to maintenance mode (we use 4 datanodes in this test)
> 2. Create multiple keys  (after loading the data, we check that 3 datanodes 
> are ~60% busy, and the one that is in maintenance mode is empty)
> 4. Start datanode recommission (wait until datanode recommissioning is 
> completed)
> 5. Start container balancer (wait until container balancer is completed)
> 6. Check results (after balancing on all 4 datanodes, we should see 
> approximately the same data distribution.)



--
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