impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Hecht (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-4504: fix races in PlanFragmentExecutor regarding status reporting
Date Tue, 29 Nov 2016 20:08:04 GMT
Dan Hecht has posted comments on this change.

Change subject: IMPALA-4504: fix races in PlanFragmentExecutor regarding status reporting

Patch Set 3:

File be/src/runtime/

PS3, Line 295: FragmentComplete(open_status_);
> Note that Close() always gets called. Do you think it would be simpler to m
I thought about that but purposely wanted to avoid making RPCs in Close(), because when Sailesh
was fixing those datastream sender failure cases, we decided to avoid the pattern of putting
RPCs in Close because there is nowhere to bubble status up to. i.e. Close() would be about
only local teardown, not interprocess teardown which added FlushFinal() for).

Ultimately, I think we should consider moving all of this logic into FES (or it's predecessor)
so that (a) it all happens in one place and (b) to eliminate the need for the callback indirection.

PS3, Line 315: report_thread_started_cv_
> Not your bug, but this is prone to spurious wakeups. Should be:

> But also, now I think of it - FragmentExecState::Exec() checks to see if Pr
Yeah, that's what I meant in the commit message about cleaning up the interactions. I'll go
one step further to see if it seems better.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I052b7b4fabb341ad27ad294cd5b0a53728d87d0e
Gerrit-PatchSet: 3
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Dan Hecht <>
Gerrit-Reviewer: Dan Hecht <>
Gerrit-Reviewer: Henry Robinson <>
Gerrit-HasComments: Yes

View raw message