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 A994E200CE6 for ; Fri, 1 Sep 2017 07:45:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A7E9616C842; Fri, 1 Sep 2017 05:45:04 +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 EECFF16C83A for ; Fri, 1 Sep 2017 07:45:03 +0200 (CEST) Received: (qmail 32999 invoked by uid 500); 1 Sep 2017 05:45:03 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 32983 invoked by uid 99); 1 Sep 2017 05:45:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Sep 2017 05:45:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 69453C3735 for ; Fri, 1 Sep 2017 05:45:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ctcRj-w2xcvs for ; Fri, 1 Sep 2017 05:45:01 +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 7EEF15FCC1 for ; Fri, 1 Sep 2017 05:45:01 +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 EC4B3E028F for ; Fri, 1 Sep 2017 05:45:00 +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 4648B24147 for ; Fri, 1 Sep 2017 05:45:00 +0000 (UTC) Date: Fri, 1 Sep 2017 05:45:00 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 01 Sep 2017 05:45:04 -0000 Lars Hofhansl created PHOENIX-4148: -------------------------------------- Summary: COUNT(DISTINCT(...)) should have a memory size limit Key: PHOENIX-4148 URL: https://issues.apache.org/jira/browse/PHOENIX-4148 Project: Phoenix Issue Type: Bug Reporter: Lars Hofhansl I just managed to kill (hang) a region server by issuing a COUNT(DISTINCT(...)) query over a column with very high cardinality (20m in this case). This is perhaps not a useful thing to do, but Phoenix should nonetheless not allow to have a server fail because of a query. [~jamestaylor], I see there GlobalMemoryManager, but I do not quite see how I'd get a reference to one, once needs a tenant id, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)