[
https://issues.apache.org/jira/browse/HBASE-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003990#comment-14003990
]
Devaraj Das commented on HBASE-11214:
-------------------------------------
Yes, we could use the same pool. The issue is, as I said before, we would then
need to keep a track of which task completed because in that case, we would
have two types of tasks in the pool - one the "scan" and another "close". We
would have to pass in more information etc. when we schedule a task... Also
when a "scan" task completes, we cancel the other redundant scan tasks. This
would also need to be aware that it shouldn't cancel the "close" tasks.
In summary, it's doable very much but it's more code... Having two pools
doesn't harm anything and these are internal implementation classes, not
user-visible..
> Fixes for scans on a replicated table
> -------------------------------------
>
> Key: HBASE-11214
> URL: https://issues.apache.org/jira/browse/HBASE-11214
> Project: HBase
> Issue Type: Sub-task
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: hbase-10070
>
> Attachments: 11214-1.txt
>
>
> During testing with the IT in HBASE-10818, found an issue to do with how
> "close" of scanners was handled.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
