[
https://issues.apache.org/jira/browse/HDDS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604913#comment-16604913
]
Shashikant Banerjee commented on HDDS-297:
------------------------------------------
Thanks [~szetszwo], for the review.Patch v11 addresses your review comments.
..what are the possible /PipelineActionPipelineAction(s)? Currently, we only
has one.
Yes, we currently have only one action that is closing the pipeline. With 2
node failure handling, we may (or may not) need to add more actions like moving
pipeline to quasi closed state.
testCloseContainerEventWithRatis failure is happening probably using
MockNodeManger for initializing the ratis pipeline which is failing.
Will be addressing the failure in a separate jira.
> Add pipeline actions in Ozone
> -----------------------------
>
> Key: HDDS-297
> URL: https://issues.apache.org/jira/browse/HDDS-297
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-297.001.patch, HDDS-297.002.patch,
> HDDS-297.003.patch, HDDS-297.004.patch, HDDS-297.005.patch,
> HDDS-297.006.patch, HDDS-297.007.patch, HDDS-297.008.patch,
> HDDS-297.009.patch, HDDS-297.010.patch, HDDS-297.011.patch
>
>
> Pipeline in Ozone are created out of a group of nodes depending upon the
> replication factor and type. These pipeline provide a transport protocol for
> data transfer.
> Inorder to detect any failure of pipeline, SCM should receive pipeline
> reports from Datanodes and process it to identify various raft rings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
