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

Gao Jhih Cyuan reassigned HDDS-8010:
------------------------------------

    Assignee: Gao Jhih Cyuan

> Improve DN warning message when getBlock does not find the block
> ----------------------------------------------------------------
>
>                 Key: HDDS-8010
>                 URL: https://issues.apache.org/jira/browse/HDDS-8010
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Wei-Chiu Chuang
>            Assignee: Gao Jhih Cyuan
>            Priority: Major
>
> We found the following message in DN but the message isn't clear:
> (1) should print the block id
> (2) the message should be logged at WARN level.
> {noformat}
> 2023-02-21 18:44:42,304 INFO 
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler: Operation: 
> GetBlock , Trace ID:  , Message: Unable to find the block. , Result: 
> NO_SUCH_BLOCK , StorageContainerExce
> ption Occurred.
> org.apache.hadoop.hdds.scm.container.common.helpers.StorageContainerException:
>  Unable to find the block.
>         at 
> org.apache.hadoop.ozone.container.keyvalue.impl.BlockManagerImpl.getBlockByID(BlockManagerImpl.java:359)
>         at 
> org.apache.hadoop.ozone.container.keyvalue.impl.BlockManagerImpl.getBlock(BlockManagerImpl.java:256)
>         at 
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler.handleGetBlock(KeyValueHandler.java:578)
>         at 
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler.dispatchRequest(KeyValueHandler.java:246)
>         at 
> org.apache.hadoop.ozone.container.keyvalue.KeyValueHandler.handle(KeyValueHandler.java:220)
>         at 
> org.apache.hadoop.ozone.container.common.impl.HddsDispatcher.dispatchRequest(HddsDispatcher.java:320)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to