[
https://issues.apache.org/jira/browse/IMPALA-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287106#comment-17287106
]
Grant Henke commented on IMPALA-10519:
--------------------------------------
Outside of the change to allow configuration of the `num_reactors` is there an
"easy" way for users to understand what value to set num_reactors too? Is there
enough data in an Impala profile to help understand that the num_reactors is
the bottleneck?
> Allow setting of num_reactors for KuduClient
> --------------------------------------------
>
> Key: IMPALA-10519
> URL: https://issues.apache.org/jira/browse/IMPALA-10519
> Project: IMPALA
> Issue Type: Improvement
> Affects Versions: Impala 4.0
> Reporter: Thomas Tauber-Marshall
> Assignee: Thomas Tauber-Marshall
> Priority: Major
>
> The KuduClient allows setting a number of reactor threads, which are used for
> sending rpcs to Kudu such as for scans. Impala does not currently set this
> value, so it defaults to 4 threads, which may be too few for many use cases,
> since there is a single KuduClient per impalad. We should determine a better
> default (eg. based on the number of cpu cores) and also expose a flag to make
> it configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
