hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashikant Banerjee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-676) Enable Read from open Containers via Standalone Protocol
Date Fri, 19 Oct 2018 09:06:00 GMT

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

Shashikant Banerjee commented on HDDS-676:

Patch v4 addresses the javaodc, checkstyle and failed test cases.

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

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

View raw message