From issues-return-5010-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Fri Mar 8 20:29:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E20F318067C for ; Fri, 8 Mar 2019 21:29:04 +0100 (CET) Received: (qmail 16733 invoked by uid 500); 8 Mar 2019 20:29:04 -0000 Mailing-List: contact issues-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 issues@phoenix.apache.org Received: (qmail 16724 invoked by uid 99); 8 Mar 2019 20:29:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2019 20:29:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 88469C28BC for ; Fri, 8 Mar 2019 20:29:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 0zDekZIm5LFX for ; Fri, 8 Mar 2019 20:29:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 73F3F61148 for ; Fri, 8 Mar 2019 20:29: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 7A4F4E2808 for ; Fri, 8 Mar 2019 20:29: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 1A58F257D9 for ; Fri, 8 Mar 2019 20:29:00 +0000 (UTC) Date: Fri, 8 Mar 2019 20:29:00 +0000 (UTC) From: "Vincent Poon (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-5131) Make spilling to disk for order/group by configurable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-5131?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 788273#comment-16788273 ]=20 Vincent Poon commented on PHOENIX-5131: --------------------------------------- [~abhishek.chouhan] for SizeBoundQueue, do we need to decrement currentSize= when polling? I guess in your usage it might not matter as you only offer= once? but might still be good to have. Is there any difference between `context.getConnection().getQueryServices()= .getProps()` and `services.getProps()` ? Also, can we cache these properti= es in a field at factory creation, or are you expecting them to be dynamica= lly changed? Also, I notice in some places thresholdByes is an int, and in others a long= . We should probably keep it long everywhere > Make spilling to disk for order/group by configurable > ----------------------------------------------------- > > Key: PHOENIX-5131 > URL: https://issues.apache.org/jira/browse/PHOENIX-5131 > Project: Phoenix > Issue Type: Improvement > Reporter: Abhishek Singh Chouhan > Assignee: Abhishek Singh Chouhan > Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: PHOENIX-5131-master-v2.patch, PHOENIX-5131-master-v2= .patch, PHOENIX-5131-master.patch, PHOENIX-5131-master.patch > > > We've observed that large queries, doing order/group by=C2=A0leading to i= ssues on the regionserver (crashes/long gc pauses/file handler exhaustion e= tc.). We should make spilling to disk configurable and in case its disabled= , fail the query once it hits the spilling limit on any of the region serve= rs. Also make=C2=A0spooling threshold server-side property only to prevent = clients from controlling memory allocation on the rs side. -- This message was sent by Atlassian JIRA (v7.6.3#76005)