You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/05/02 20:56:00 UTC
[jira] [Work logged] (HDDS-1448) RatisPipelineProvider should only
consider open pipeline while excluding dn for pipeline allocation
[ https://issues.apache.org/jira/browse/HDDS-1448?focusedWorklogId=236553&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-236553 ]
ASF GitHub Bot logged work on HDDS-1448:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/May/19 20:55
Start Date: 02/May/19 20:55
Worklog Time Spent: 10m
Work Description: avijayanhwx commented on issue #786: HDDS-1448 : RatisPipelineProvider should only consider open pipeline …
URL: https://github.com/apache/hadoop/pull/786#issuecomment-488828795
We also have to add the pipelines in ALLOCATED state to the set of DNs being excluded. The reason is that when the SCMPipelineManager initializes the set of pipelines from the pipeline store (RocksDB) in the ALLOCATED state. Hence, when the background pipeline creator gets the current pipeline list for creating pipelines pro-actively, if we fail to exclude these "ALLOCATED" pipelines which may soon transition to "OPEN", we can end up creating duplicate pipelines in the same DN ring.
If the ALLOCATED state becomes OPEN, then it remains a NO-Op and if it transitions to CLOSED, the background pipeline will automatically start using the DNs in the next creation.
cc @mukul1987 / @nandakumar131 / @arp7 Can you comment if the above makes sense?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 236553)
Time Spent: 40m (was: 0.5h)
> RatisPipelineProvider should only consider open pipeline while excluding dn for pipeline allocation
> ---------------------------------------------------------------------------------------------------
>
> Key: HDDS-1448
> URL: https://issues.apache.org/jira/browse/HDDS-1448
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Affects Versions: 0.3.0
> Reporter: Mukul Kumar Singh
> Assignee: Aravindan Vijayan
> Priority: Major
> Labels: MiniOzoneChaosCluster, pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> While allocation pipelines, Ratis pipeline provider considers all the pipelines irrespective of the state of the pipeline. This can lead to case where all the datanodes are up but the pipelines are in closing state in SCM.
--
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