Siyao Meng created HDDS-17512:
---------------------------------
Summary: Add a Recon metric for task status write failures
Key: HDDS-17512
URL: https://issues.apache.org/jira/browse/HDDS-17512
Project: Apache Ozone
Issue Type: Improvement
Components: Ozone Recon
Reporter: Siyao Meng
After HDDS-17193, a failed write to the {{RECON_TASK_STATUS}} table in
{{ReconTaskStatusUpdater.updateDetails()}} is logged and ignored, so it no
longer fails the OM sync. The OM sync metrics ({{OzoneManagerSyncMetrics}},
{{ReconSyncMetrics}}, {{ReconTaskMetrics}}) are in-memory and stay correct, but
the table itself goes stale, and both {{ReconTaskStatusMetrics}} and the task
status API read from it. Today the only sign of this is a WARN log.
*Proposal:* add a counter for task status write failures (per task name, if
cheap) and increment it in the {{DataAccessException}} handler in
{{updateDetails()}}, so operators can see when the reported task status is
stale.
Raised in the review of https://github.com/apache/ozone/pull/11647.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
