tree c4eeb0b53e1b3bc3f8156069318e5353b28f4986
parent e3e947d8a6a960da9868f2e3fb5c22c2cc243539
author Yunze Xu <xyzinfernity@163.com> 1636624015 +0800
committer Enrico Olivelli <eolivelli@gmail.com> 1639586058 +0100

[Managed Ledger] Fix the incorrect total size when BrokerEntryMetadata is enabled (#12714)

### Motivation

When the BrokerEntryMetadata is enabled, the total size in `ManagedLedgerImpl` is inaccurate. Because when the total size is updated in `OpAddEntry#safeRun`, the `dataLength` is the initial size of `data` when `OpAddEntry` is constructed, but `data` could be changed via `setData` method.

The inaccurate total size could affect the retention size validation. Because in `ManagedLedgerImpl#internalTrimLedgers`, the total size reduces by the size of `LedgerInfo`, which is assigned from the `LedgerHandle#getLength()`. Therefore, the total size will become 0 or less before all ledgers are removed.

### Modifications

- Update `dataLength` field in `setData` method.
- Add a `testManagedLedgerTotalSize` test to `BrokerEntryMetadataE2ETest`. It produces 10 messages and trigger the rollover manually so that the first `LedgerInfo` of the managed ledger contains the correct total bytes. Then compare the `totalSize` field with it to verify this fix works.

(cherry picked from commit 5dbb7d25849f3a037aa522b5d0767801aa0a5096)