You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2022/10/25 03:32:00 UTC

[jira] [Updated] (HDDS-6025) Ozone Retry Path Optimizations

     [ https://issues.apache.org/jira/browse/HDDS-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz-wo Sze updated HDDS-6025:
-----------------------------
        Parent:     (was: HDDS-4454)
    Issue Type: Improvement  (was: Sub-task)

> Ozone Retry Path Optimizations
> ------------------------------
>
>                 Key: HDDS-6025
>                 URL: https://issues.apache.org/jira/browse/HDDS-6025
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Shashikant Banerjee
>            Priority: Major
>
> Currently, in the retry path, once a datanode goes down , the data from last acknowledged length will be retried on a new pipeline with new set of datanodes. Secondly, once a block write fails in between , a new block is allocated for the remaining unacknowledged data.
>  
> In HDFS, in case of a datanode failure,  a new datanode is recruited in case of a dn failure and the packets are only written for the replcaed datanode. Also, the same block gets written out and there is no new block allocation. In that way, the key/file metadata remains same but in ozone, it may bloat up the OM metadata.
>  
> This Jira is to discuss any optimizations needed in ozone retry path to improve performance if any, 



--
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