[
https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789188#comment-16789188
]
Hadoop QA commented on HDDS-1209:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} HDDS-1209 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDDS-1209 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12961915/HDDS-1209-002.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDDS-Build/2494/console |
| Powered by | Apache Yetus 0.10.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Fix the block allocation logic in SCM when client wants to exclude all
> available open containers in a chosen pipeline
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-1209
> URL: https://issues.apache.org/jira/browse/HDDS-1209
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Shashikant Banerjee
> Assignee: Aravindan Vijayan
> Priority: Major
> Attachments: HDDS-1209-000.patch, HDDS-1209-001.patch,
> HDDS-1209-002.patch
>
>
> As per [~nandakumar131] comments here in HDDS-726 ,
> https://issues.apache.org/jira/browse/HDDS-726?focusedCommentId=16779554&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16779554
> We may end up in case in SCM where all the open containers available in a
> chosen pipeline are there in the exclude list provided by client during
> allocate block call. In such case, blockMamager in SCM will run in an
> infinite loop. This needs to be fixed as a part of this jira.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
