phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Wong (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5231) Configurable Stats Cache
Date Tue, 28 May 2019 18:27:00 GMT


Daniel Wong commented on PHOENIX-5231:

I was trying to come up with a fix I think would be clearer but Im still traveling and don't
have good internet access outside my phone.  I think we can construct a better fix as the
one you proposed here removes the standard META-INF directory approach that one would normally
expect the services to live in.  Let me see if I can spend a little time and construct something.

> Configurable Stats Cache
> ------------------------
>                 Key: PHOENIX-5231
>                 URL:
>             Project: Phoenix
>          Issue Type: Test
>            Reporter: Daniel Wong
>            Assignee: Daniel Wong
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0
>         Attachments: 5231-quickfix-v2.txt, 5231-quickfix.txt, PHOENIX-5231.4.x-HBase-1.3.patch,
PHOENIX-5231.4.x-HBase-1.3.v2.patch, PHOENIX-5231.4.x-HBase-1.3.v3.patch, PHOENIX-5231.master.v3.patch,
>          Time Spent: 8h 40m
>  Remaining Estimate: 0h
> Currently, the phoenix stats cache is per ConnectionQuerySerivce/ConnectionProfile, which
leads to duplicated cached entry (the guideposts) and waste resources if these separate connections
are querying the same underlying table. It would be good to be able to provide a configurable
stats cache as control the cache level so it could be per JVM.

This message was sent by Atlassian JIRA

View raw message