[
https://issues.apache.org/jira/browse/PHOENIX-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327965#comment-14327965
]
Jeffrey Zhong commented on PHOENIX-1675:
----------------------------------------
{quote}
I believe if we're using a DirectExecutorService, we'd lose this.
{quote}
I think you're right about this. Actually even HTable reads will use parallel
reads, for example, in region replica case and latest scan code path. We should
have a separate thread pool for HTable(or let HTable manage its own) and a
different thread pool for Phoenix usage. So we have a good separation between
hbase client & Phoenix space otherwise any internal changes in HBase client
side may cause unexpected behaviors.
> Improve Phoenix client threading
> --------------------------------
>
> Key: PHOENIX-1675
> URL: https://issues.apache.org/jira/browse/PHOENIX-1675
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Attachments: PHOENIX-1675_wip.patch
>
>
> See PHOENIX-971 for some interesting threading discussions. Moving here for
> further discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
