[HDFS-12471] Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG

• Type: Sub-task
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: HDFS-7240
• Hadoop Flags: Reviewed
• Assignee: Weiwei Yang
• Reporter: Xiaoyu Yao
• Created: 15/Sep/17 18:08
• Updated: 26/Apr/18 21:54
• Resolved: 03/Oct/17 21:14

Description

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],Weiwei Yang, Yuanbo Liu.

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