[
https://issues.apache.org/jira/browse/HDDS-9754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840234#comment-17840234
]
Ethan Rose commented on HDDS-9754:
----------------------------------
So I actually got the repro test to pass, but it takes 5 minutes for the client
to finish writing the small amount of data. I tried this with both low and high
(the default) values of \{{ozone.client.failover.max.attempts}} and
\{{ozone.client.wait.between.retries.millis}} and neither affect the runtime. I
then realized these seem to only affect retires against the OM, not datanodes.
Even though the test eventually finishes, 5 minutes is still way too long. We
may be falling back to Ratis client timeout/retry logic here.
> Ozone Client Does not Retry on a New Pipeline
> ---------------------------------------------
>
> Key: HDDS-9754
> URL: https://issues.apache.org/jira/browse/HDDS-9754
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode, SCM
> Reporter: Ethan Rose
> Priority: Major
> Attachments: pipeline_retry_repro.diff
>
>
> During testing, we observed that when the client was given bad pipeline, it
> continued trying to write to it forever, making it stuck indefinitely. The
> client should eventually give up on the write and get a different pipeline
> from OM.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
