[ https://issues.apache.org/jira/browse/HBASE-20226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166068#comment-17166068 ]
Bharath Vissapragada commented on HBASE-20226: ---------------------------------------------- bq. This is related to the work going on in HBASE-21098. It's likely that this Jira is no longer needed after that work is concluded. [~zyork] Why is this no longer needed? I think the attached patch parallelizes deletes by adding them to a thread pool while the parent jira (HBASE-21098) doesn't do it right? We are running into bottlenecks on this sequential delete and I saw this jira. Did I miss something? > Performance Improvement Taking Large Snapshots In Remote Filesystems > -------------------------------------------------------------------- > > Key: HBASE-20226 > URL: https://issues.apache.org/jira/browse/HBASE-20226 > Project: HBase > Issue Type: Improvement > Components: snapshots > Affects Versions: 1.4.0 > Environment: HBase 1.4.0 running on an AWS EMR cluster with the > hbase.rootdir set to point to a folder in S3 > Reporter: Saad Mufti > Priority: Minor > Attachments: HBASE-20226..01.patch > > > When taking a snapshot of any table, one of the last steps is to delete the > region manifests, which have already been rolled up into a larger overall > manifest and thus have redundant information. > This proposal is to do the deletion in a thread pool bounded by > hbase.snapshot.thread.pool.max . For large tables with a lot of regions, the > current single threaded deletion is taking longer than all the rest of the > snapshot tasks when the Hbase data and the snapshot folder are both in a > remote filesystem like S3. > I have a patch for this proposal almost ready and will submit it tomorrow for > feedback, although I haven't had a chance to write any tests yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)