You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ranganath Govardhanagiri (Jira)" <ji...@apache.org> on 2024/07/03 11:39:00 UTC
[jira] [Assigned] (PHOENIX-7298) Expose client metric for GET_TABLE_REGIONS_FAIL errors
[ https://issues.apache.org/jira/browse/PHOENIX-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ranganath Govardhanagiri reassigned PHOENIX-7298:
-------------------------------------------------
Assignee: Ranganath Govardhanagiri
> Expose client metric for GET_TABLE_REGIONS_FAIL errors
> ------------------------------------------------------
>
> Key: PHOENIX-7298
> URL: https://issues.apache.org/jira/browse/PHOENIX-7298
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Assignee: Ranganath Govardhanagiri
> Priority: Major
>
> We don't have any metrics to track the failure to retrieve metadata region location lookups while running a query. We should expose a counter metric in GlobalClientMetrics that can help track the num of failures to retrieve metadata.
> We have metric COUNTER_METADATA_INCONSISTENCY that helps track failure with metadata inconsistency, however it eventually leads to GET_TABLE_REGIONS_FAIL errors. Hence, metric for GET_TABLE_REGIONS_FAIL failures would be really helpful as the underlying cause could be anything.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)