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 2016/01/23 21:38:39 UTC

[jira] [Resolved] (PHOENIX-2136) Unable to configure thread pool size used in Embeded driver.

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

James Taylor resolved PHOENIX-2136.
-----------------------------------
    Resolution: Invalid

Please ask questions on the dev or user mailing lists.

> Unable to configure thread pool size used in Embeded driver.
> ------------------------------------------------------------
>
>                 Key: PHOENIX-2136
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2136
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>            Reporter: Dhirendra Kumar Singh
>              Labels: jdbc
>
> We're using phoenix JDBC driver for propagating our changes to HBase. Changes going in are in order of millions per second. Phoenix being a Embedded driver so using a Pooled connection is out of question. While going throught the phoenix Driver code we saw that the pool size used by executor in QueryServicesImpl is using a default value 128. There isn't a way by which we can override this value as here in QueryServicesImpl we are super(defaultProps, QueryServicesOptions.withDefaults()) which would always pick 128 as default value.
> Before we go ahead, and fork to make changes for our use cases I wanted to understand what is the motivation behind this limiting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)