[HDDS-2238] Container Data Scrubber spams log in empty cluster

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.5.0
• Component/s: Ozone Datanode
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 03/Oct/19 15:51
• Updated: 24/Feb/20 20:49
• Resolved: 07/Oct/19 21:07

Description

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.:

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

Also CPU usage is quite high.

I think:

1. there should be a small sleep between iterations
2. it should log only if any containers were scanned

Issue Links

• links to: GitHub Pull Request #1590