peterxcli opened a new pull request, #8099:
URL: https://github.com/apache/ozone/pull/8099
## What changes were proposed in this pull request?
```
Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.554 s <<<
FAILURE! -- in
org.apache.hadoop.ozone.container.common.transport.server.ratis.TestContainerStateMachineFollower
org.apache.hadoop.ozone.container.common.transport.server.ratis.TestContainerStateMachineFollower.testWriteFailure(boolean)[2]
-- Time elapsed: 0.024 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <CONTAINER_UNHEALTHY> but
was: <CONTAINER_INTERNAL_ERROR>
...
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1145)
at
org.apache.hadoop.ozone.container.common.transport.server.ratis.TestContainerStateMachine.testWriteFailure(TestContainerStateMachine.java:175)
at
org.apache.hadoop.ozone.container.common.transport.server.ratis.TestContainerStateMachineFollower.testWriteFailure(TestContainerStateMachineFollower.java:23)
```
---
@chungen0126: The first write and the second write are writing to the same
entry, causing them to interfere with each other. The first write has not yet
been completed by the chunkExecutor when the second write is in progress,
causing the second write to detect the first write's entry.
So use different entry with incremental index for SM to write wont get the
[in-flight writeChunk
future](https://github.com/peterxcli/ozone/blob/d5ee708619df15ace7a4007c80e5c5a2cff9a178/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/transport/server/ratis/ContainerStateMachine.java#L578-L581)
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-12602
## How was this patch tested?
CI:
https://github.com/peterxcli/ozone/actions/runs/13899997432
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
