Fixes: #22473

Motivation

For retention policies, it should be retain/delete the ledgers which were consumed.

But currently, we determine whether to delete a ledger by ledger total size(includes un-cosumed ledgers), it is not reasonable, and leads to deleting all the consumed ledger.

And also, the threshold of backlog quota might be related to this: backlog quota limitation have to less than retention. It doesn't make sense, too.

Modifications

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: