[ 
https://issues.apache.org/jira/browse/HBASE-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388682#comment-16388682
 ] 

Mike Drob commented on HBASE-20095:
-----------------------------------

v6 looks much cleaner, thanks for addressing my comments.

Still having trouble understanding one last thing, though.

Notifications will come in serially, and sometimes we'll set that we need to 
update the pool. There could be multiple tasks going on at the same time. 
However, we shutdown the pool after the first task finishes, so we could end up 
killing a bunch of the queued/executing tasks before creating the new pool. Is 
this ok because we'll simply clean up the files on the next pass? If so, why do 
we need to wait for one task to finish at all?

> Redesign single instance pool in CleanerChore
> ---------------------------------------------
>
>                 Key: HBASE-20095
>                 URL: https://issues.apache.org/jira/browse/HBASE-20095
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Reid Chan
>            Assignee: Reid Chan
>            Priority: Critical
>         Attachments: HBASE-20095.master.001.patch, 
> HBASE-20095.master.002.patch, HBASE-20095.master.003.patch, 
> HBASE-20095.master.004.patch, HBASE-20095.master.005.patch, 
> HBASE-20095.master.006.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to