[
https://issues.apache.org/jira/browse/IMPALA-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071554#comment-18071554
]
ASF subversion and git services commented on IMPALA-14855:
----------------------------------------------------------
Commit cb4fc4e03233a7ff268e8fa8f8891e07c9643213 in impala's branch
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=cb4fc4e03 ]
IMPALA-14855: Make number of query map shards configurable
Allow configuring the number of query map shards used for tracking
queries with `--num_query_map_shards`. Retains the default of 4.
Removes unused and buggy ScopedShardedMapPBRef.
Change-Id: Icacb7fc541171546925798c2c652d60052bb774b
Reviewed-on: http://gerrit.cloudera.org:8080/24161
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
