Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CEBB5200C57 for ; Fri, 31 Mar 2017 20:14:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CD82D160B7C; Fri, 31 Mar 2017 18:14:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 27271160B80 for ; Fri, 31 Mar 2017 20:14:45 +0200 (CEST) Received: (qmail 83632 invoked by uid 500); 31 Mar 2017 18:14:44 -0000 Mailing-List: contact issues-help@impala.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@impala.incubator.apache.org Delivered-To: mailing list issues@impala.incubator.apache.org Received: (qmail 83611 invoked by uid 99); 31 Mar 2017 18:14:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Mar 2017 18:14:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 05F0F188A0F for ; Fri, 31 Mar 2017 18:14:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JG3l0CXEhuao for ; Fri, 31 Mar 2017 18:14:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D534B5FC81 for ; Fri, 31 Mar 2017 18:14:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 549DAE0A12 for ; Fri, 31 Mar 2017 18:14:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AF44621DDD for ; Fri, 31 Mar 2017 18:14:41 +0000 (UTC) Date: Fri, 31 Mar 2017 18:14:41 +0000 (UTC) From: "Dimitris Tsirogiannis (JIRA)" To: issues@impala.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IMPALA-5147) Add the ability to exclude coordinators from query execution MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 31 Mar 2017 18:14:46 -0000 Dimitris Tsirogiannis created IMPALA-5147: --------------------------------------------- Summary: Add the ability to exclude coordinators from query execution Key: IMPALA-5147 URL: https://issues.apache.org/jira/browse/IMPALA-5147 Project: IMPALA Issue Type: Sub-task 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 (v6.3.15#6346)