You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/12/21 09:26:00 UTC
[jira] [Updated] (HDDS-2351) Fix write performance issue in Non-HA OM
[ https://issues.apache.org/jira/browse/HDDS-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
mingchao zhao updated HDDS-2351:
--------------------------------
Target Version/s: 1.4.0 (was: 1.3.0)
> Fix write performance issue in Non-HA OM
> -----------------------------------------
>
> Key: HDDS-2351
> URL: https://issues.apache.org/jira/browse/HDDS-2351
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Rajesh Balamohan
> Assignee: Nandakumar
> Priority: Major
> Labels: TriagePending, performance
> Attachments: Screenshot 2019-10-23 at 2.27.05 PM.png
>
>
> HDDS-2333 enables sync option in OM non-HA mode. However, this flushes very frequently causing disk to saturate its IOPS soon. It creates way too small write workloads and disk hits limit.
> To put it in perspective, in simple write benchmark of creating keys with 10 clients, it generates {{0.33MB/s}} write workload with {{116 IOPS}}. This causes disk to saturate at 98%.
>
> !Screenshot 2019-10-23 at 2.27.05 PM.png|width=621,height=370!
>
> Reverting back HDDS-2333 fixes this issue. I see >{{10x}} degradation with HDDS-2333.
> In case non-HA is supported in OM, it would be good to call it out. Currently, code explicitly enables sync option. [https://github.com/apache/hadoop-ozone/commit/c6c9794fc590371ad9c3b8fdcd7a36ed42909b40#diff-3ed3ab4891d7b4fa31ca96740b78ae5bR261]
>
> I used {{commit 1baa5a158d13f469c12bef86ef288d60ef0eee85}} in master branch.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org