You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2015/02/19 02:39:11 UTC

[jira] [Commented] (PHOENIX-1675) Improve Phoenix client threading

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

Samarth Jain commented on PHOENIX-1675:
---------------------------------------

+1 to the idea of using DirectExecutorService. 

Are you suggesting that we have a separate thread pool for getting HTable in MutationState? If we use DirectExecutorService, getting an HTable will be using the request thread itself. By request thread I mean the thread which called commit(). So it shouldn't be that bad. Even if we use a thread pool, the parent request thread would still need to wait for a thread in the pool to return the HTable. What do you think? [~jamestaylor]

> 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)