You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Rushabh Shah (Jira)" <ji...@apache.org> on 2023/05/31 22:47:00 UTC

[jira] [Comment Edited] (PHOENIX-6968) Create RegionServerCoprocessor to invalidate cache.

    [ https://issues.apache.org/jira/browse/PHOENIX-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728162#comment-17728162 ] 

Rushabh Shah edited comment on PHOENIX-6968 at 5/31/23 10:46 PM:
-----------------------------------------------------------------

Cc [~vjasani] [~palashc] [~tkhurana]


was (Author: shahrs87):
Cc [~vjasani] [~palashc]

> Create RegionServerCoprocessor to invalidate cache.
> ---------------------------------------------------
>
>                 Key: PHOENIX-6968
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6968
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Rushabh Shah
>            Priority: Major
>
> Whenever we update metadata (like alter table add column, drop table), we need to invalidate metadata cache entry (introduced by phoenix-6943) on all the regionservers which has that cache entry. First step would be to issue an invalidate command on all the regionservers irrespective of whether that regionserver has the cache entry. We can further optimize by invalidating only on RS that has that cache entry.
> We need to have co-processor method something like invalidateCache(CacheEntry) and since we maintain this cache at the regionserver level, we can add it in RegionServerObserver/RegionServerCoprocessor and add this coprocessor to all the regionservers.
> Recently [~vjasani] added ReplicationSinkEndpoint/ReplicationSinkCompatEndpoint in 
> PHOENIX-5521. We can rename that to PhoenixRegionObserver/PhoenixRegionServerCoprocessor so that we can consolidate all the endpoints in the same class.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)