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

Lokesh Jain commented on HDDS-1868:
-----------------------------------

[~swagle] In the patch below condition would only be true for the leader 
datanode.

 
{code:java}
        if (reply.getRoleInfoProto().hasLeaderInfo()) {
          reports.add(PipelineReport.newBuilder()
              .setPipelineID(
                  PipelineID.valueOf(groupId.getUuid()).getProtobuf())
              .build());
        }
{code}
We would end up sending Pipeline Report only from leader to SCM. SCM should 
ideally receive pipeline reports from all datanodes in a pipeline in order to 
mark the pipeline as OPEN.

The follower does get a roleInfoProto but 
reply.getRoleInfoProto().hasLeaderInfo() for a follower is false as it does not 
have leaderInfo but a followerInfo.

 

> Ozone pipelines should be marked as ready only after the leader election is 
> complete
> ------------------------------------------------------------------------------------
>
>                 Key: HDDS-1868
>                 URL: https://issues.apache.org/jira/browse/HDDS-1868
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode, SCM
>    Affects Versions: 0.4.0
>            Reporter: Mukul Kumar Singh
>            Assignee: Siddharth Wagle
>            Priority: Major
>             Fix For: 0.5.0
>
>         Attachments: HDDS-1868.01.patch
>
>
> Ozone pipeline on restart start in allocated state, they are moved into open 
> state after all the pipeline have reported to it. However this potentially 
> can lead into an issue where the pipeline is still not ready to accept any 
> incoming IO operations.
> The pipelines should be marked as ready only after the leader election is 
> complete and leader is ready to accept incoming IO.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

Reply via email to