[ 
https://issues.apache.org/jira/browse/HDDS-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-17820:
----------------------------------
    Labels: pull-request-available  (was: )

> Add SCM metrics for storage-tier placement failures by requested storage type 
> and reason
> ----------------------------------------------------------------------------------------
>
>                 Key: HDDS-17820
>                 URL: https://issues.apache.org/jira/browse/HDDS-17820
>             Project: Apache Ozone
>          Issue Type: Task
>            Reporter: Devesh Kumar Singh
>            Assignee: Devesh Kumar Singh
>            Priority: Major
>              Labels: pull-request-available
>
> When SCM cannot place data on the requested tier, it matters whether it was 
> short of space or of suitable nodes. Today this is only logged. On the Ratis 
> write path the result code is also lost: WritableRatisContainerProvider 
> catches the SCMException and rethrows a plain IOException.
> Add a counter with the labels requestedTier and reason (no_space / 
> no_suitable_node / other). Increment it where the result code is still known. 
> This JIRA does not change which failures may fall back; that is HDDS-17535.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to