Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
On a moderately loaded cluster, name node logs are flooded with entries of INFO BlockStateChange..., to the tune of ~30 lines per millisecond. This provides operators with little to no usable information. I suggest reducing this log message to DEBUG. Perhaps this information (and other logging related to it) should be directed to a dedicated block-audit.log file that can be queried, rotated on a separate schedule from the log of the main process.