hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mukul Kumar Singh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-324) Use pipeline name as Ratis groupID to allow datanode to report pipeline info
Date Thu, 09 Aug 2018 10:14:01 GMT

     [ https://issues.apache.org/jira/browse/HDDS-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mukul Kumar Singh updated HDDS-324:
-----------------------------------
    Attachment: HDDS-324.003.patch

> 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message