Ethan Rose created HDDS-11509:
---------------------------------
Summary: Logging improvements for deletion services
Key: HDDS-11509
URL: https://issues.apache.org/jira/browse/HDDS-11509
Project: Apache Ozone
Issue Type: Sub-task
Components: OM, Ozone Datanode, SCM
Reporter: Ethan Rose
All Ozone components involved in background deletion should follow consistent
patterns with their logging:
* At the end of each run, and INFO log should display how many items were
processed, what the current limit of items per run is, and how long it took.
** If the run time of the iteration exceeded the configured interval, the
message should highlight this and be elevated to WARN.
*** This should also log the config keys that can remedy this for batch size,
interval, or number of threads.
* Either during or after each run, a DEBUG log should indicate each individual
item that was processed.
These changes should be applied uniformly across the following background
services, which may be split into separate sub-tasks:
* OM open key cleanup
* OM key delete
* OM directory delete
* SCM block delete
* Datanode block delete
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
