[jira] [Updated] (HDDS-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated HDDS-844: --- Resolution: Fixed Fix Version/s: 0.4.0 Status: Resolved (was: Patch Available) Thanks for the contribution [~ljain]. I have committed this to trunk. > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Fix For: 0.4.0 > > Attachments: HDDS-844.001.patch, HDDS-844.002.patch, > HDDS-844.003.patch, HDDS-844.004.patch, HDDS-844.005.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-844: - Attachment: HDDS-844.005.patch > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: HDDS-844.001.patch, HDDS-844.002.patch, > HDDS-844.003.patch, HDDS-844.004.patch, HDDS-844.005.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-844: - Attachment: HDDS-844.004.patch > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: HDDS-844.001.patch, HDDS-844.002.patch, > HDDS-844.003.patch, HDDS-844.004.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-844: - Attachment: HDDS-844.003.patch > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: HDDS-844.001.patch, HDDS-844.002.patch, > HDDS-844.003.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-844: - Attachment: HDDS-844.002.patch > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: HDDS-844.001.patch, HDDS-844.002.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-844: - Attachment: HDDS-844.001.patch > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: HDDS-844.001.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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-844) Add logic for pipeline teardown after timeout
[ https://issues.apache.org/jira/browse/HDDS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-844: - Status: Patch Available (was: Open) > Add logic for pipeline teardown after timeout > - > > Key: HDDS-844 > URL: https://issues.apache.org/jira/browse/HDDS-844 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Affects Versions: 0.4.0 >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: HDDS-844.001.patch > > > On receiving pipeline action we close the pipeline and wait for all > containers to get closed. Currently pipeline is destroyed on datanodes only > after all the containers have been closed. There is a possibility for > containers to never get to CLOSED state if there is a two node failure. In > such scenarios the pipeline needs to be destroyed and removed from SCM after > a timeout. -- 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
