[
https://issues.apache.org/jira/browse/IMPALA-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-14855.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Make the number of shards in the ShardedQueryMap configurable
> -------------------------------------------------------------
>
> Key: IMPALA-14855
> URL: https://issues.apache.org/jira/browse/IMPALA-14855
> Project: IMPALA
> Issue Type: Task
> Components: Backend
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> ShardedQueryMap currently uses a hard coded NUM_QUERY_BUCKETS (4) for the
> number of shards. In some clusters, we have seen cases where there is
> contention on the shard's lock. It would be useful to be able to tune this at
> startup.
> A different problem is that something can do expensive computation or take
> other locks while holding the shard's lock (e.g. DoFuncForAllEntries). That
> will need to be addressed separately.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
