You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 04:36:39 UTC

[jira] [Resolved] (PHOENIX-1435) Create unit test that uses 15K guideposts

     [ https://issues.apache.org/jira/browse/PHOENIX-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor resolved PHOENIX-1435.
-----------------------------------
    Resolution: Won't Fix

> Create unit test that uses 15K guideposts
> -----------------------------------------
>
>                 Key: PHOENIX-1435
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1435
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: PHOENIX-1435.patch, PHOENIX-1435_v2.patch
>
>
> We're seeing memory issues when 14K guideposts are used to execute a query. Although other issues are contributing to the high number of guideposts (PHOENIX-1434), and we don't need to execute some LIMIT queries in parallel (PHOENIX-1432), we should still get to the bottom of why this is causing memory and/or CPU issues.
> One question with this kind of scenario - why didn't the query get rejected, as it seems like it would fill up the queue past the allowed 5000 threads? Also, do the temp files get cleaned up in this scenario?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)