Sailesh Mukil has uploaded this change for review. ( http://gerrit.cloudera.org:8080/8455
Change subject: IMPALA-6144: UpdateFilter()/PublishFilter() continue to run after query failure/cancellation ...................................................................... IMPALA-6144: UpdateFilter()/PublishFilter() continue to run after query failure/cancellation The Coordinator::UpdateFilter() and Coordinator::PublishFilter() functions do not check for query failure/cancellation. So if runtime filters are being aggregated/published during a failure, they will not be cancelled and still be sent out which may take a while depending on the size of the cluster. Also, these functions could potentially hold very large amounts of untracked memory. This patch fixes it by checking for cancellation in both the functions. Change-Id: I400456ad85adb9c23d2d432d772311fa4dcff2ed --- M be/src/runtime/coordinator-backend-state.cc M be/src/runtime/coordinator.cc 2 files changed, 3 insertions(+), 0 deletions(-) git pull ssh://gerrit.cloudera.org:29418/Impala-ASF refs/changes/55/8455/1 -- To view, visit http://gerrit.cloudera.org:8080/8455 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: I400456ad85adb9c23d2d432d772311fa4dcff2ed Gerrit-Change-Number: 8455 Gerrit-PatchSet: 1 Gerrit-Owner: Sailesh Mukil <sail...@cloudera.com>
