You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/02/19 02:22:11 UTC

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

     [ https://issues.apache.org/jira/browse/PHOENIX-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-1675:
----------------------------------
    Attachment: PHOENIX-1675_wip.patch

Here's a patch for the idea I had to not go through a pool for HTable access, since we've already gone through a pool. One tweak would be to have a third pool for our writers (which occur in MutationState). In this case, we may want a thread pool, because Phoenix doesn't parallelize writes, but let's HBase do this. FYI, [~jeffreyz].

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