[
https://issues.apache.org/jira/browse/HDDS-9551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791326#comment-17791326
]
Dave Teng edited comment on HDDS-9551 at 11/29/23 9:22 PM:
-----------------------------------------------------------
sure, thanks [~adoroszlai] for the headsup!
And yeah, I think regarding to [~umamaheswararao] 's concern, on SCM the server
side, there is already logic to create new pipeline if no pipeline found
available with client's initial request.
(https://github.com/apache/ozone/blob/master/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/pipeline/WritableRatisContainerProvider.java#L112-L121)
And the creation of pipeline would only make use of those DN which are
HEALTHY and IN_SERVICE.
([https://github.com/apache/ozone/blob/master/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/pipeline/RatisPipelineProvider.java#L237-L238])
so, I think for [~umamaheswararao] 's case, other healthy DN would take care of
the pipeline creation. This looks to be fine as long as there are enough
healthy DN to create pipeline.
was (Author: JIRAUSER292649):
sure, thanks [~adoroszlai] for the headsup!
And yeah, I think regarding to [~umamaheswararao] 's concern, on SCM the server
side, there is already logic to create new pipeline if no pipeline found
available with client's initial request. And the creation of pipeline would
only make use of those DN which are HEALTHY and IN_SERVICE.
(https://github.com/apache/ozone/blob/master/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/pipeline/RatisPipelineProvider.java#L237-L238)
so, I think for [~umamaheswararao] 's case, other healthy DN would take care of
the pipeline creation. This looks to be fine as long as there are enough
healthy DN to create pipeline.
> Allow the client write to fall back to nodes in the exclude list if that is
> all that is available
> -------------------------------------------------------------------------------------------------
>
> Key: HDDS-9551
> URL: https://issues.apache.org/jira/browse/HDDS-9551
> Project: Apache Ozone
> Issue Type: Task
> Components: Ozone Client
> Reporter: Dave Teng
> Assignee: Dave Teng
> Priority: Major
> Labels: pull-request-available
>
> Allow the client write to fall back to nodes in the exclude list if that is
> all that is available
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]