[
https://issues.apache.org/jira/browse/PHOENIX-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793942#comment-17793942
]
ASF GitHub Bot commented on PHOENIX-7111:
-----------------------------------------
shahrs87 commented on PR #1744:
URL: https://github.com/apache/phoenix/pull/1744#issuecomment-1843778294
> Maybe the second invalidation is not needed when a new index is created
since none of the region servers know about it yet, or can we piggy back the
table invalidation on the index invalidation?
What is the index state before and after the update?
> Metrics for server-side metadata cache
> --------------------------------------
>
> Key: PHOENIX-7111
> URL: https://issues.apache.org/jira/browse/PHOENIX-7111
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Palash Chauhan
> Assignee: Palash Chauhan
> Priority: Major
>
> Add metrics for monitoring the new metadata caching design.
> # Time taken to invalidate cache on all region servers during a DDL operation
> # Number of failed DDL operations due to failure in cache invalidation
> # Number of validateLastDDLTimestamp requests per region-server
> # Cache hits/misses per region-server when validating timestamps
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
