[
https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189377#comment-16189377
]
Yiqun Lin commented on HDFS-12471:
----------------------------------
Hi [~cheersyang], how is the going of this JIRA?
> Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
> -------------------------------------------------------------------
>
> Key: HDFS-12471
> URL: https://issues.apache.org/jira/browse/HDFS-12471
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Xiaoyu Yao
> Assignee: Weiwei Yang
>
> Looks like we are logging a few no-op messages every minute in KSM/SCM log.
> Should we reduce the log level to DEBUG or TRACE? cc: [~anu],[~cheersyang],
> [~yuanbo].
> {code}
> 2017-09-14 23:42:15,022 [SCMBlockDeletingService#0] INFO
> (SCMBlockDeletingService.java:103) - Running
> DeletedBlockTransactionScanner
> 2017-09-14 23:42:15,024 [SCMBlockDeletingService#0] INFO
> (SCMBlockDeletingService.java:136) - Scanned deleted blocks log and got 0
> delTX to process
> 2017-09-14 23:42:24,139 [KeyDeletingService#1] INFO
> (KeyDeletingService.java:123) - No pending deletion key found in KSM
> 2017-09-14 23:43:09,377 [BlockDeletingService#2] INFO
> (BlockDeletingService.java:109) - Plan to choose 10 containers for block
> deletion, actually returns 0 valid containers.
> 2017-09-14 23:43:15,027 [SCMBlockDeletingService#0] INFO
> (SCMBlockDeletingService.java:103) - Running
> DeletedBlockTransactionScanner
> 2017-09-14 23:43:15,027 [SCMBlockDeletingService#0] INFO
> (SCMBlockDeletingService.java:136) - Scanned deleted blocks log and got 0
> delTX to process
> 2017-09-14 23:43:24,146 [KeyDeletingService#1] INFO
> (KeyDeletingService.java:123) - No pending deletion key found in KSM
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
