[
https://issues.apache.org/jira/browse/IMPALA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477564#comment-16477564
]
ASF subversion and git services commented on IMPALA-5384:
---------------------------------------------------------
Commit 0e6117be3be8475ea1aa727dec55979cbffd05b7 in impala's branch
refs/heads/2.x from [~dhecht]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=0e6117b ]
IMPALA-7033/IMPALA-7030: Backout suspected change leading to crash
Revert "IMPALA-5384, part 2: Simplify Coordinator locking and clarify state"
This reverts commit 6ca87e46736a1e591ed7d7d5fee05b4b4d2fbb50.
Change-Id: Idc63006e6e04130b2873a6a9730e434c563327c5
Reviewed-on: http://gerrit.cloudera.org:8080/10412
Reviewed-by: Tim Armstrong <tarmstr...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Reviewed-on: http://gerrit.cloudera.org:8080/10423
Reviewed-by: Dan Hecht <dhe...@cloudera.com>
> 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: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
