[
https://issues.apache.org/jira/browse/HDDS-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937952#comment-16937952
]
Siddharth Wagle commented on HDDS-1868:
---------------------------------------
Hi [~ljain], regarding 3., the setLeaderId is called for leader as well so
_notifyLeader_ is not needed, right? Agree to trigger HB right away.
4. Good catch, I missed the multi-raft point.
" Can we keep it simple so that we call pipeline.reportDatanode(dn) once a
pipeline report with leaderId set is received?" -> Not sure I follow, when we
receive HB from 3rd DN with leaderID we need to open pipeline, so we do need to
maintain PipelineID -> LeaderIDSet map to know if all 3 reported. That's what
you meant right?
> 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, HDDS-1868.02.patch,
> HDDS-1868.03.patch, HDDS-1868.04.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.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
