[
https://issues.apache.org/jira/browse/HDFS-16992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716593#comment-17716593
]
ASF GitHub Bot commented on HDFS-16992:
---------------------------------------
hfutatzhanghb opened a new pull request, #5594:
URL: https://github.com/apache/hadoop/pull/5594
recently, we found lots of logs like below which trigger logWarn alarm：
```
WARN org.apache.hadoop.hdfs.StateChange: BLOCK* internalReleaseLease: All
existing blocks are COMPLETE, lease removed, file /xxx/xxx/d_tmp.000402_0
closed.
```
the log is in FSNamesystem#internalReleaseLease method which can be set to
info level rather than warn level actually.
> change log level in FSNamesystem#internalReleaseLease method
> ------------------------------------------------------------
>
> Key: HDFS-16992
> URL: https://issues.apache.org/jira/browse/HDFS-16992
> Project: Hadoop HDFS
> Issue Type: Wish
> Components: namenode
> Affects Versions: 3.3.5
> Reporter: farmmamba
> Priority: Trivial
>
> recently, we found lots of logs like below which trigger logWarn alarm：
> {code:java}
> WARN org.apache.hadoop.hdfs.StateChange: BLOCK* internalReleaseLease: All
> existing blocks are COMPLETE, lease removed, file /xxx/xxx/d_tmp.000402_0
> closed.{code}
> the log is in FSNamesystem#internalReleaseLease method which can be set to
> info level rather than warn level actually.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
