phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karan Mehta (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5069) Use asynchronous refresh to provide non-blocking Phoenix Stats Client Cache
Date Wed, 13 Feb 2019 13:22:00 GMT


Karan Mehta commented on PHOENIX-5069:

Patch committed to master (5.x-HBase-2.0) and 4.x-HBase-1.4 branches. 

> Use asynchronous refresh to provide non-blocking Phoenix Stats Client Cache
> ---------------------------------------------------------------------------
>                 Key: PHOENIX-5069
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Bin Shi
>            Assignee: Bin Shi
>            Priority: Major
>         Attachments: PHOENIX-5069-4.14.1-hbase-1.3-phoenix-stats.001.patch, PHOENIX-5069-4.14.1-hbase-1.3-phoenix-stats.002.patch,
PHOENIX-5069.4.x-HBase-1.4.001.patch, PHOENIX-5069.master.001.patch, PHOENIX-5069.master.002.patch,
PHOENIX-5069.master.003.patch, PHOENIX-5069.master.004.patch, PHOENIX-5069.patch
>          Time Spent: 6h 40m
>  Remaining Estimate: 0h
> The current Phoenix Stats Cache uses TTL based eviction policy. A cached entry will expire
after a given amount of time (900s by default) passed since the entry's been created. This
will lead to cache miss when Compiler/Optimizer fetches stats from cache at the next time.
As you can see from the above graph, fetching stats from the cache is a blocking operation
— when there is cache miss, it has a round trip over the wire to scan the SYSTEM.STATS Table
and to get the latest stats info, rebuild the cache and finally return the stats to the Compiler/Optimizer.
Whenever there is a cache miss, this blocking call causes significant performance penalty and
see periodic spikes.
> *This Jira suggests to use asynchronous refresh mechanism to provide a non-blocking
cache. For details, please see the linked design document below.*
> [~karanmehta93] [] [~dbwong] [~elserj] [] [~sergey

This message was sent by Atlassian JIRA

View raw message