[
https://issues.apache.org/jira/browse/IMPALA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Hecht reopened IMPALA-5384:
-------------------------------
I backed out the last change because it's suspected that it causes IMPALA-7033.
I think thre is a problem with StartBackendExec() running concurrently withÂ
HandleExecStateTransition() which can happen while still starting other
finstances.
> Simplify coordinator locking protocol
> -------------------------------------
>
> Key: IMPALA-5384
> URL: https://issues.apache.org/jira/browse/IMPALA-5384
> Project: IMPALA
> Issue Type: Improvement
> Affects Versions: Impala 2.9.0
> Reporter: Marcel Kornacker
> Assignee: Dan Hecht
> Priority: Major
> Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> The coordinator has a central lock (lock_) which is used very liberally to
> synchronize state changes that don't need to be synchronized, creating a
> concurrency bottleneck.
> Also, the coordinator contains a number of data structures related to INSERT
> finalization that don't need to be part of and synchronized with the rest of
> the coordinator state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
