[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1209: -- Resolution: Fixed Fix Version/s: 0.5.0 0.4.0 Status: Resolved (was: Patch Available) Thanks [~avijayan] for the contribution and [~shashikant] for reporting this. Committed this to branch ozone-0.4 and trunk. > 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 > Fix For: 0.4.0, 0.5.0 > > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1209: -- Target Version/s: 0.4.0 > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Attachment: (was: HDDS-1209-002.patch) > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Status: Open (was: Patch Available) > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Status: Patch Available (was: Open) > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Attachment: HDDS-1209-002.patch > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Status: Open (was: Patch Available) > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Attachment: HDDS-1209-002.patch Status: Patch Available (was: Open) Thanks for the review comments [~nandakumar131]. I have addressed them in the current patch. > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Attachment: HDDS-1209-001.patch Status: Patch Available (was: Open) Fix checkstyle issue. > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Status: Open (was: Patch Available) > 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=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Status: Patch Available (was: Open) I wanted to take a stab at fixing this. Please review when you have a chance. [~nandakumar131] | [~bharatviswa] | [~ljain] | [~shashikant] > 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 > > > As per [~nandakumar131] comments here in HDDS-726 , > https://issues.apache.org/jira/browse/HDDS-726?focusedCommentId=16779554=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
[jira] [Updated] (HDDS-1209) Fix the block allocation logic in SCM when client wants to exclude all available open containers in a chosen pipeline
[ https://issues.apache.org/jira/browse/HDDS-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated HDDS-1209: Attachment: HDDS-1209-000.patch > 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 > > > As per [~nandakumar131] comments here in HDDS-726 , > https://issues.apache.org/jira/browse/HDDS-726?focusedCommentId=16779554=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
