[jira] [Updated] (HDFS-12471) Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
[
https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anu Engineer updated HDFS-12471:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: HDFS-7240
Status: Resolved (was: Patch Available)
[~xyao] Thanks for filing the issue. [~linyiqun] Thanks for comments.
[~cheersyang] Thanks for the contribution. I have committed this to the feature
branch.
> 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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12471) Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
[
https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated HDFS-12471:
---
Status: Patch Available (was: Open)
> 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
> 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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12471) Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
[
https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated HDFS-12471:
---
Priority: Trivial (was: Major)
> 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
> 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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12471) Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
[
https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated HDFS-12471:
---
Attachment: HDFS-12471-HDFS-7240.001.patch
Thanks [~linyiqun] for the reminder, I have uploaded a patch to reduce some of
INFO logging to DEBUG. Please help to review if you have a chance, thanks.
> 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
> 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
(v6.4.14#64029)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12471) Ozone: Reduce some KSM/SCM deletion log messages from INFO to DEBUG
[
https://issues.apache.org/jira/browse/HDFS-12471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDFS-12471:
-
Issue Type: Sub-task (was: Bug)
Parent: HDFS-7240
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
