[
https://issues.apache.org/jira/browse/HDDS-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736849#comment-17736849
]
Stephen O'Donnell commented on HDDS-8897:
-----------------------------------------
Also, what have you got set for ozone.scm.ec.pipeline.minimum? The default is
5, which is much too low. With 25 nodes and 24 disks, you probably want 25 *24
/ EC_Nodes (eg 9 for 6-3), which would give 66. That is the algorithm we have
recently moved to. If you are running with the default, there are probably too
few pipelines and it will be causing a higher rate of pipeline closing and
opening.
> ec container has too high latency when allocate blocks
> ------------------------------------------------------
>
> Key: HDDS-8897
> URL: https://issues.apache.org/jira/browse/HDDS-8897
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: GuoHao
> Assignee: Stephen O'Donnell
> Priority: Blocker
> Labels: pull-request-available
> Attachments: image-2023-06-21-21-58-15-052.png,
> image-2023-06-21-21-58-50-518.png, image-2023-06-21-23-53-56-534.png
>
>
> ec container has too high latency when allocate blocks
>
> I use ec in a high concurrency situation, I configure the metric on scm, and
> as concurrency gradually increases, the latency of the allocate block
> increases.
>
> allocate block ops：
> !image-2023-06-21-21-58-50-518.png!
>
> average latency：
> !image-2023-06-21-21-58-15-052.png!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
