[ 
https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788166#comment-16788166
 ] 

Aravindan Vijayan edited comment on HDDS-1209 at 3/8/19 7:19 PM:
-----------------------------------------------------------------

There can be a case where we have 2 available pipelines (P1 & P2) in 
allocateBlock after filtering, and say we pick P1 (random). If the containers 
in P1 are in excluded containers list, according to current logic, we decide to 
create a new container in that pipeline. Is that action preferred over using 
the other available pipeline (P2)?



was (Author: avijayan):
There can be a case where we have 2 available pipelines (P1 & P2) in 
allocateBlock after filtering, and say we pick P1 (random). If the the 
containers in P1 are in excluded containers list, according to current logic, 
we decide to create a new container in that pipeline. Is that action preferred 
over using the other available pipeline (P2)?


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

Reply via email to