[jira] [Updated] (HDDS-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-383: -- Fix Version/s: (was: 0.3.0) 0.2.1 > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch, > HDDS-383.03.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated HDDS-383: - Resolution: Fixed Status: Resolved (was: Patch Available) I have committed this. Thanks, [~shashikant]! > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.3.0 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch, > HDDS-383.03.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anu Engineer updated HDDS-383: -- Fix Version/s: (was: 0.2.1) 0.3.0 > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.3.0 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch, > HDDS-383.03.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Attachment: HDDS-383.03.patch > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch, > HDDS-383.03.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Attachment: HDDS-383.02.patch > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Attachment: (was: HDDS-383.02.patch) > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Attachment: HDDS-383.02.patch > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch, HDDS-383.02.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Status: Patch Available (was: Open) > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Attachment: HDDS-383.01.patch > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch, HDDS-383.01.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Attachment: HDDS-383.00.patch > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-383.00.patch > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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-383) Ozone Client should discard preallocated blocks from closed containers
[ https://issues.apache.org/jira/browse/HDDS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated HDDS-383: - Summary: Ozone Client should discard preallocated blocks from closed containers (was: Ozone Client should cache closed container Info to discard preallocated blocks from closed containers) > Ozone Client should discard preallocated blocks from closed containers > -- > > Key: HDDS-383 > URL: https://issues.apache.org/jira/browse/HDDS-383 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: Ozone Client >Reporter: Shashikant Banerjee >Assignee: Shashikant Banerjee >Priority: Major > Fix For: 0.2.1 > > > When key write happens in Ozone client, based on the initial size given, > preallocation of blocks happen. While write happens, containers can get > closed and if the remaining preallocated blocks belong to closed containers > , they can be discarded right away instead of trying to write these blocks > and failing with exception. This Jira aims to address this. -- 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
