[
https://issues.apache.org/jira/browse/HDDS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580331#comment-16580331
]
Hudson commented on HDDS-324:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14769 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14769/])
HDDS-324. Addendum: remove the q letter which is accidentally added to (elek:
rev 7e822ec246fa78dd140192e1e800f0205aca037a)
* (edit) hadoop-common-project/hadoop-common/src/main/bin/hadoop-functions.sh
> Use pipeline name as Ratis groupID to allow datanode to report pipeline info
> ----------------------------------------------------------------------------
>
> Key: HDDS-324
> URL: https://issues.apache.org/jira/browse/HDDS-324
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 0.2.1
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-324.001.patch, HDDS-324.002.patch,
> HDDS-324.003.patch, HDDS-324.004.patch, HDDS-324.005.patch,
> HDDS-324.006.patch, HDDS-324.007.patch, HDDS-324.008.patch,
> HDDS-324.009-addendum.patch, HDDS-324.009.patch
>
>
> Currently Ozone creates a random pipeline id for every pipeline where a
> pipeline consist of 3 nodes in a ratis ring. Ratis on the other hand uses the
> notion of RaftGroupID which is a unique id for the nodes in a ratis ring.
> When a datanode sends information to SCM, the pipeline for the node is
> currently identified using dn2PipelineMap. With correct use of RaftGroupID,
> we can eliminate the use of dn2PipelineMap.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
