[jira] [Resolved] (IMPALA-5897) impala concurrent query test

["Michael Brown (JIRA)" <ji...@apache.org>]

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

Michael Brown resolved IMPALA-5897.
-----------------------------------
    Resolution: Information Provided

Hello [~yucong], you probably want to increase {{-fe_service_threads}}:

{noformat}
    -fe_service_threads (number of threads available to serve client requests)
      type: int32 default: 64
{noformat}

This is a confusing thing that has come up before. I'm going to file a docs Jira to add a note about this.

Also, don't forget you can check and use the [users|http://mail-archives.apache.org/mod_mbox/incubator-impala-user/] email list for such questions in the future.

Thanks for your interest in Impala!

> impala concurrent query test
> ----------------------------
>
>                 Key: IMPALA-5897
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5897
>             Project: IMPALA
>          Issue Type: Question
>         Environment: centos6.4   kernel: 2.6.32-642.el6.x86_64 ,cdh5.12.0 ,impala2.8.0
>            Reporter: yucong
>         Attachments: screenshot-1.png
>
>
> We use jmeter for concurrent testing, the use of the latest jdbc driver, the results reached 60 concurrent impala can not connect, but impala-shell can still work, jdbc drive class is com.cloudera.impala.jdbc4.Driver, jdbc URL is jdbc : impala: //192.168.3.153: 21050 / test, and then I used the UseNativeQuery = 1 parameter, still can not solve this problem,it is mean impala use jdbc connect max concurrent query is 50 ? 
> the cluster has 8 node，each one have e7 4830 32 core，128G mem



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)