StevenLuMT

execute `/pulsar/bin/bookkeeper shell readlog 1884` to get all Lid and Eid Then execute `/pulsar/bin/bookkeeper shell readledger` to read the data. I understand that readledger will check the **index** and **entryLog**,...

All parameters are assigned, refer to the following example: ``` bookieId=***:3181 lid=17772 eidStart=0 eidEnd= 7005 ./bin/bookkeeper shell readledger -bookie $bookieId -msg -ledgerid $lid -firstentryid $eidStart -lastentryid $eidEnd ```

``` export BOOKIE_CONF=/pulsar/conf/bookkeeper.conf lid=17772 ./bin/bookkeeper shell ledgermetadata -ledgerid $lid |grep LedgerMetadata ``` Get the ensembles where the ledgerId is located ``` export BOOKIE_CONF=/pulsar/conf/bookkeeper.conf # bookieId cannot be customized and must...

Well, currently it seems that ledgerId=17772 has been expired and cleared, which is in line with expectations; there are other ledgerIds in the current entrgLog?

Well, the size is indeed a problem, but it may also be because the gc task finally merged the data.

Our XHS team(@liangyepianzhou @AuroraTwinkle @StevenLuMT @cai152) will submit a few to [pulsar-java-contrib](https://github.com/StevenLuMT/pulsar-java-contrib) as a primer to let everyone know the role of this library

please fix the checkstyle issue, thanks @horizonzy

reopen's reason: rerun failure checks

reopen's reason: rerun failure checks

reopen's reason: rerun failure checks