[jira] [Updated] (HDDS-4232) Use single thread for KeyDeletingService
[ https://issues.apache.org/jira/browse/HDDS-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai updated HDDS-4232: --- Labels: (was: pull-request-available) > Use single thread for KeyDeletingService > > > Key: HDDS-4232 > URL: https://issues.apache.org/jira/browse/HDDS-4232 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Fix For: 1.1.0 > > > KeyDeletingService scan the keys from a particular rocksdb table and sends > deletion request to SCM. Every thread would scan the table and send deletion > requests. This can lead to multiple deletion request for a particular block. > There is currently no way to distribute the keys to be deleted amongst > multiple threads. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4232) Use single thread for KeyDeletingService
[ https://issues.apache.org/jira/browse/HDDS-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-4232: -- Description: KeyDeletingService scan the keys from a particular rocksdb table and sends deletion request to SCM. Every thread would scan the table and send deletion requests. This can lead to multiple deletion request for a particular block. There is currently no way to distribute the keys to be deleted amongst multiple threads. (was: KeyDeletingService and OpenKeyCleanupService scan the keys from a particular rocksdb table and sends deletion request to SCM. Every thread would scan the table and send deletion requests. This can lead to multiple deletion request for a particular block. There is currently no way to distribute the keys to be deleted amongst multiple threads.) > Use single thread for KeyDeletingService > > > Key: HDDS-4232 > URL: https://issues.apache.org/jira/browse/HDDS-4232 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Labels: pull-request-available > > KeyDeletingService scan the keys from a particular rocksdb table and sends > deletion request to SCM. Every thread would scan the table and send deletion > requests. This can lead to multiple deletion request for a particular block. > There is currently no way to distribute the keys to be deleted amongst > multiple threads. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4232) Use single thread for KeyDeletingService
[ https://issues.apache.org/jira/browse/HDDS-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-4232: -- Summary: Use single thread for KeyDeletingService (was: Use single thread for KeyDeletingService and OpenKeyCleanupService) > Use single thread for KeyDeletingService > > > Key: HDDS-4232 > URL: https://issues.apache.org/jira/browse/HDDS-4232 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Labels: pull-request-available > > KeyDeletingService and OpenKeyCleanupService scan the keys from a particular > rocksdb table and sends deletion request to SCM. Every thread would scan the > table and send deletion requests. This can lead to multiple deletion request > for a particular block. There is currently no way to distribute the keys to > be deleted amongst multiple threads. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-4232) Use single thread for KeyDeletingService and OpenKeyCleanupService
[ https://issues.apache.org/jira/browse/HDDS-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-4232: - Labels: pull-request-available (was: ) > Use single thread for KeyDeletingService and OpenKeyCleanupService > -- > > Key: HDDS-4232 > URL: https://issues.apache.org/jira/browse/HDDS-4232 > Project: Hadoop Distributed Data Store > Issue Type: Bug >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Labels: pull-request-available > > KeyDeletingService and OpenKeyCleanupService scan the keys from a particular > rocksdb table and sends deletion request to SCM. Every thread would scan the > table and send deletion requests. This can lead to multiple deletion request > for a particular block. There is currently no way to distribute the keys to > be deleted amongst multiple threads. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
