phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5131) Make spilling to disk for order/group by configurable
Date Thu, 14 Mar 2019 19:07:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792966#comment-16792966
] 

Hadoop QA commented on PHOENIX-5131:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12962518/PHOENIX-5131-4.x-HBase-1.2.patch
  against 4.x-HBase-1.2 branch at commit 05b99018a77805cd92411c26bd4147e62cbf7281.
  ATTACHMENT ID: 12962518

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 9 new or modified
tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/2426//console

This message is automatically generated.

> 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-4.x-HBase-1.2.patch, PHOENIX-5131-4.x-HBase-1.3.patch,
PHOENIX-5131-4.x-HBase-1.4.patch, PHOENIX-5131-master-v2.patch, PHOENIX-5131-master-v2.patch,
PHOENIX-5131-master-v3.patch, PHOENIX-5131-master-v4.patch, PHOENIX-5131-master.patch, PHOENIX-5131-master.patch
>
>
> We've observed that large queries, doing order/group by leading to issues on the regionserver
(crashes/long gc pauses/file handler exhaustion etc.). 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
servers. Also make spooling 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)

Mime
View raw message