[
https://issues.apache.org/jira/browse/PHOENIX-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Palash Chauhan resolved PHOENIX-7883.
-------------------------------------
Resolution: Fixed
> Rework metrics for the Phoenix Eventually Consistent Index framework
> ---------------------------------------------------------------------
>
> Key: PHOENIX-7883
> URL: https://issues.apache.org/jira/browse/PHOENIX-7883
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.3.1
> Reporter: Palash Chauhan
> Assignee: Palash Chauhan
> Priority: Major
> Fix For: 5.4.0, 5.3.2
>
>
> h4. Background
> Eventually consistent (EC) secondary indexes in Phoenix are maintained
> asynchronously by {{{}IndexCDCConsumer{}}}, which drains the CDC index for
> each region and replays mutations into the secondary-index tables. The
> current observability surface defined by {{MetricsIndexCDCConsumerSource}}
> was sufficient to validate the feature in tests but is not sufficient to
> operate it safely in production.
> *Goal*
> Make freshness, liveness, and correctness of the EC index pipeline directly
> observable
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
