[jira] [Updated] (HDDS-273) DeleteLog entries should be purged only after corresponding dns commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-273: - Attachment: HDDS-273.004.patch > DeleteLog entries should be purged only after corresponding dns commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Critical > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch, HDDS-273.002.patch, > HDDS-273.003.patch, HDDS-273.004.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding DNs commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-273: --- Summary: DeleteLog entries should be purged only after corresponding DNs commit the transaction (was: DeleteLog entries should be purged only after corresponding dns commit the transaction) > DeleteLog entries should be purged only after corresponding DNs commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Critical > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch, HDDS-273.002.patch, > HDDS-273.003.patch, HDDS-273.004.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding DNs commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated HDDS-273: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the contribution [~ljain]. I have committed this to trunk. > DeleteLog entries should be purged only after corresponding DNs commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Critical > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch, HDDS-273.002.patch, > HDDS-273.003.patch, HDDS-273.004.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding dns commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-273: - Status: Patch Available (was: Open) > DeleteLog entries should be purged only after corresponding dns commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding dns commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-273: - Attachment: HDDS-273.001.patch > DeleteLog entries should be purged only after corresponding dns commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding dns commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-273: - Attachment: HDDS-273.002.patch > DeleteLog entries should be purged only after corresponding dns commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch, HDDS-273.002.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding dns commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-273: - Attachment: HDDS-273.003.patch > DeleteLog entries should be purged only after corresponding dns commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch, HDDS-273.002.patch, > HDDS-273.003.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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-273) DeleteLog entries should be purged only after corresponding dns commit the transaction
[ https://issues.apache.org/jira/browse/HDDS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HDDS-273: -- Priority: Critical (was: Major) > DeleteLog entries should be purged only after corresponding dns commit the > transaction > -- > > Key: HDDS-273 > URL: https://issues.apache.org/jira/browse/HDDS-273 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Components: SCM >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Critical > Fix For: 0.2.1 > > Attachments: HDDS-273.001.patch, HDDS-273.002.patch, > HDDS-273.003.patch > > > Currently DeleteBlockLogImpl removes an entry corresponding to a deleteBlock > as soon as it receives an acknowledgement from a single DN. The entries > should be deleted only after all corresponding dns give an acknowledgement > for the delete command. -- 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
