Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.5.0
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:
- there should be a small sleep between iterations
- it should log only if any containers were scanned
Attachments
Issue Links
- links to