hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mukul Kumar Singh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-226) Client should update block length in OM while committing the key
Date Tue, 31 Jul 2018 17:21:00 GMT

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

Mukul Kumar Singh updated HDDS-226:
-----------------------------------
    Attachment: HDDS-226.09.patch

> Client should update block length in OM while committing the key
> ----------------------------------------------------------------
>
>                 Key: HDDS-226
>                 URL: https://issues.apache.org/jira/browse/HDDS-226
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Manager
>            Reporter: Mukul Kumar Singh
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-226.00.patch, HDDS-226.01.patch, HDDS-226.02.patch, HDDS-226.03.patch,
HDDS-226.04.patch, HDDS-226.05.patch, HDDS-226.06.patch, HDDS-226.07.patch, HDDS-226.08.patch,
HDDS-226.09.patch
>
>
> Currently the client allocate a key of size with SCM block size, however a client can
always write smaller amount of data and close the key. The block length in this case should
be updated on OM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message