impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dimitris Tsirogiannis (JIRA)" <>
Subject [jira] [Resolved] (IMPALA-5147) Add the ability to exclude coordinators from query execution
Date Mon, 01 May 2017 17:58:04 GMT


Dimitris Tsirogiannis resolved IMPALA-5147.
    Resolution: Fixed

Change-Id: I5d2ff7f341c9d2b0649e4d14561077e166ad7c4d
Reviewed-by: Dimitris Tsirogiannis <>
Tested-by: Impala Public Jenkins
M be/src/scheduling/
M be/src/scheduling/scheduler-test-util.h
M be/src/scheduling/
M be/src/scheduling/
M be/src/scheduling/scheduler.h
M be/src/service/
M be/src/service/impala-http-handler.h
M be/src/service/
M be/src/service/impala-server.h
M be/src/util/
M be/src/util/
M bin/
M common/thrift/StatestoreService.thrift
M tests/common/
M tests/custom_cluster/
M www/backends.tmpl
M www/root.tmpl
17 files changed, 432 insertions(+), 307 deletions(-)

  Impala Public Jenkins: Verified
  Dimitris Tsirogiannis: Looks good to me, approved

> Add the ability to exclude coordinators from query execution
> ------------------------------------------------------------
>                 Key: IMPALA-5147
>                 URL:
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend
>            Reporter: Dimitris Tsirogiannis
>            Assignee: Dimitris Tsirogiannis
> The fix for IMPALA-4041 added the ability to limit the set of nodes that can coordinate
Impala queries and hence receive catalog updates. However, with this change coordinators can
and will still participate in query execution. That may introduce in some cases significant
load in the coordinator node. To address this issue, we should introduce another flag, termed
is_executor, to exclude certain nodes from participating in query execution. 

This message was sent by Atlassian JIRA

View raw message