You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Duong (Jira)" <ji...@apache.org> on 2022/09/15 00:47:00 UTC
[jira] [Comment Edited] (HDDS-7223) Caching container location information in OM
[ https://issues.apache.org/jira/browse/HDDS-7223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605015#comment-17605015 ]
Duong edited comment on HDDS-7223 at 9/15/22 12:46 AM:
-------------------------------------------------------
Proposed design document: [https://docs.google.com/document/d/1-hVdA7mRBFiFOqr0J0Pg6-Ie5SOZaT7Z].
was (Author: JIRAUSER290990):
Design document: https://docs.google.com/document/d/1-hVdA7mRBFiFOqr0J0Pg6-Ie5SOZaT7Z.
> Caching container location information in OM
> --------------------------------------------
>
> Key: HDDS-7223
> URL: https://issues.apache.org/jira/browse/HDDS-7223
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Duong
> Priority: Major
>
> A container can move and change the Datanode details in it's lifecycle post close of a container.
> When a key needs to be read by the client, OM queries SCM to update the location information for a container. This adds additional latency per request and load on SCM which is directly proportional to the read load on OM.
> This Jira is track the design and implementation of improving read performance by addressing this code path.
--
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