[
https://issues.apache.org/jira/browse/PHOENIX-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150119#comment-16150119
]
James Taylor commented on PHOENIX-4148:
---------------------------------------
Use null as the tenantId. See example in GroupedAggregateRegionObserver of
{{GlobalCache.getTenantCache(env, tenantId)}} and this javadoc:
{code}
/**
* Get the tenant cache associated with the tenantId. If tenantId is not
applicable, null may be
* used in which case a global tenant cache is returned.
* @param env the HBase configuration
* @param tenantId the tenant ID or null if not applicable.
* @return TenantCache
*/
public static TenantCache getTenantCache(RegionCoprocessorEnvironment env,
ImmutableBytesPtr tenantId) {
{code}
> 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
>
> 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)
