You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Abhishek Singh Chouhan (JIRA)" <ji...@apache.org> on 2019/03/07 01:09:00 UTC
[jira] [Commented] (PHOENIX-5131) Make spilling to disk for
order/group by configurable
[ https://issues.apache.org/jira/browse/PHOENIX-5131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786268#comment-16786268 ]
Abhishek Singh Chouhan commented on PHOENIX-5131:
-------------------------------------------------
[~tdsilva] [~vincentpoon] Patch that creates separate properties for enabling/disabling spooling for orderby/sort merge joins, makes server side spooling threshold separate property that is not controlled by client. Also does a bunch of refactoring around different types of queues we use in iterators.
> 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.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)