[ https://issues.apache.org/jira/browse/HDDS-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anu Engineer updated HDDS-2238: ------------------------------- Fix Version/s: 0.5.0 Resolution: Fixed Status: Resolved (was: Patch Available) Committed to the trunk > Container Data Scrubber spams log in empty cluster > -------------------------------------------------- > > Key: HDDS-2238 > URL: https://issues.apache.org/jira/browse/HDDS-2238 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: Ozone Datanode > Affects Versions: 0.5.0 > Reporter: Attila Doroszlai > Assignee: Attila Doroszlai > Priority: Major > Labels: pull-request-available > Fix For: 0.5.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > In an empty cluster (without closed containers) logs are filled with messages > from completed data scrubber iterations (~3600 per second for me), if > Container Scanner is enabled ({{hdds.containerscrub.enabled=true}}), eg.: > {noformat} > datanode_1 | 2019-10-03 15:43:57 INFO ContainerDataScanner:114 - Completed > an iteration of container data scrubber in 0 minutes. Number of iterations > (since the data-node restart) : 6763, Number of containers scanned in this > iteration : 0, Number of unhealthy containers found in this iteration : 0 > {noformat} > Also CPU usage is quite high. > I think: > # there should be a small sleep between iterations > # it should log only if any containers were scanned -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org