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] [Commented] (HDDS-339) Add block length and blockId in PutKeyResponse
Date Fri, 10 Aug 2018 18:18:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576669#comment-16576669
] 

Mukul Kumar Singh commented on HDDS-339:
----------------------------------------

Thanks for the contribution [~shashikant]. I have committed this to trunk.

> Add block length and blockId in PutKeyResponse
> ----------------------------------------------
>
>                 Key: HDDS-339
>                 URL: https://issues.apache.org/jira/browse/HDDS-339
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Client, Ozone Datanode
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-339.00.patch, HDDS-339.01.patch
>
>
> The putKey response will include blockId as well committed block length in the PutKey
response. This will be extended to include blockCommitSequenceId as well all of which will
be updated on Ozone Master. This all be required to add validation as well handle 2 node failure.



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