[HDDS-11509] Logging improvements for deletion services

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: OM, Ozone Datanode, SCM
• Labels: pull-request-available
• Assignee: Tejaskriya Madhan
• Reporter: Ethan Rose
• Created: 30/Sep/24 20:22
• Updated: Yesterday 08:42

Description

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

Issue Links

• links to: GitHub Pull Request #7314