[ https://issues.apache.org/jira/browse/IMPALA-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475391#comment-16475391 ]
ASF subversion and git services commented on IMPALA-5384: --------------------------------------------------------- Commit 33f90cc74b3003c7657d003f522dc2cf20b3ba0c in impala's branch refs/heads/master from [~dhecht] [ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=33f90cc ] Add a missing PrintId() For consistency, add a PrintId() around a query_id() used in a stream, which was missing from this commit: IMPALA-5384, part 2: Simplify Coordinator locking and clarify state This change was put into the cherry-pick for 2.x, so: Cherry-picks: not for 2.x Change-Id: I701115fb7bc88cd034ddb7f0b99cf067ef2a7078 Reviewed-on: http://gerrit.cloudera.org:8080/10391 Reviewed-by: Tim Armstrong <tarmstr...@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenk...@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 > > 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