hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12471) Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
Date Tue, 24 Apr 2018 20:57:08 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451054#comment-16451054
] 

Hudson commented on HDFS-12471:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-12471. Ozone: Reduce some KSM/SCM deletion log messages from INFO (aengineer: rev 9796d60e610dafb55d23a16e865ad37c2faefbfd)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/utils/BackgroundService.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/scm/block/SCMBlockDeletingService.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/ozone/ksm/KeyDeletingService.java


> 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
>            Priority: Trivial
>             Fix For: HDFS-7240
>
>         Attachments: HDFS-12471-HDFS-7240.001.patch
>
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message