hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HDDS-676) Enable Read from open Containers via Standalone Protocol
Date Mon, 22 Oct 2018 05:36:00 GMT

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

Anu Engineer edited comment on HDDS-676 at 10/22/18 5:35 AM:
-------------------------------------------------------------

bq. I feel blockID is used to uniquely identify a block in the system but the BCSID of a block
may be different in different non closed container replica. BCSID should not be necessarily
a part of BlockId.

I am trying to understand this more. Block Commit Sequence ID is associated with a block?
That let us identify the generation number of a block. Why is it not the part of the identity
of a block? 


was (Author: anu):
bq. I feel blockID is used to uniquely identify a block in the system but the BCSID of a block
may be different in different non closed container replica. BCSID should not be necessarily
a part of BlockId.

I am trying to understand this more. Block Commit Sequence ID is associated to a block? That
let us identity the generation number of a block. Why is it not the part of the identity of
a block? 

> Enable Read from open Containers via Standalone Protocol
> --------------------------------------------------------
>
>                 Key: HDDS-676
>                 URL: https://issues.apache.org/jira/browse/HDDS-676
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>         Attachments: HDDS-676.001.patch, HDDS-676.002.patch, HDDS-676.003.patch, HDDS-676.004.patch,
HDDS-676.005.patch, HDDS-676.006.patch
>
>
> With BlockCommitSequenceId getting updated per block commit on open containers in OM
as well datanode, Ozone Client reads can through Standalone protocol not necessarily requiring
Ratis. Client should verify the BCSID of the container which has the data block , which should
always be greater than or equal to the BCSID of the block to be read and the existing block
BCSID should exactly match that of the block to be read. As a part of this, Client can try
to read from a replica with a supplied BCSID and failover to the next one in case the block
does ont exist on one replica.



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