[jira] [Updated] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit
[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4148: -- Fix Version/s: 5.0.0 > 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 >Assignee: Lars Hofhansl >Priority: Major > Fix For: 4.14.0, 5.0.0 > > Attachments: 4148.txt, PHOENIX-4148_v2.patch > > > 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 (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit
[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4148: -- Attachment: PHOENIX-4148_v2.patch > 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 >Assignee: Lars Hofhansl >Priority: Major > Fix For: 4.14.0 > > Attachments: 4148.txt, PHOENIX-4148_v2.patch > > > 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 (v7.6.3#76005)
[jira] [Updated] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit
[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4148: -- Fix Version/s: 4.13.0 > 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 > Fix For: 4.13.0 > > 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)
[jira] [Updated] (PHOENIX-4148) COUNT(DISTINCT(...)) should have a memory size limit
[ https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-4148: --- Attachment: 4148.txt 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)
