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 6BC6E200C4E for ; Thu, 23 Mar 2017 00:22:45 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6A536160B91; Wed, 22 Mar 2017 23:22: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 B2ED6160B86 for ; Thu, 23 Mar 2017 00:22:44 +0100 (CET) Received: (qmail 84865 invoked by uid 500); 22 Mar 2017 23:22:43 -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 84856 invoked by uid 99); 22 Mar 2017 23:22:43 -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; Wed, 22 Mar 2017 23:22:43 +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 922C51812EB for ; Wed, 22 Mar 2017 23:22:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.349 X-Spam-Level: X-Spam-Status: No, score=-99.349 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652, 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 UQVvsZeED_1X for ; Wed, 22 Mar 2017 23:22: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 BC3115FB97 for ; Wed, 22 Mar 2017 23:22: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 16B25E0458 for ; Wed, 22 Mar 2017 23:22: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 BF254254E5 for ; Wed, 22 Mar 2017 23:22:41 +0000 (UTC) Date: Wed, 22 Mar 2017 23:22:41 +0000 (UTC) From: "Henry Robinson (JIRA)" To: issues@impala.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IMPALA-5109) Increase plan fragment startup histogram max latency to > 20000ms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 22 Mar 2017 23:22:45 -0000 Henry Robinson created IMPALA-5109: -------------------------------------- Summary: Increase plan fragment startup histogram max latency to > 20000ms Key: IMPALA-5109 URL: https://issues.apache.org/jira/browse/IMPALA-5109 Project: IMPALA Issue Type: Improvement Components: Distributed Exec Affects Versions: Impala 2.8.0 Reporter: Henry Robinson Assignee: Henry Robinson We track plan fragment start latencies, but max out at 20s in the histogram. We should probably set that to 30 minutes or so to capture really long RPC delays. -- This message was sent by Atlassian JIRA (v6.3.15#6346)