[
https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162503#comment-16162503
]
Lars Hofhansl edited comment on PHOENIX-4148 at 9/12/17 5:03 AM:
-----------------------------------------------------------------
Here's the clumsy patch I mentioned. Just handles one the cases for testing.
DON'T COMMIT.
I don't like it, at the same time I cannot think of anything better.
Just parking it here for now.
was (Author: lhofhansl):
Here's the clumsy patch I mentioned.
DON'T COMMIT.
I don't like it, at the same time I cannot think of anything better.
Just parking it here for now.
> 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
> Attachments: 4148.txt
>
>
> 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)
