The broker reports an error: No such entry

**Describe the bug**
pulsar version: 2.8.1
bookkeeper config: journalWriteData=false

**error log:**

```
10:55:04.879 [BookKeeperClientWorker-OrderedExecutor-12-0] ERROR org.apache.pulsar.broker.service.persistent.PersistentDispatcherMultipleConsumers - [persistent://teg_onion_onion_common_data_nj/teg_onion_onion_common_data_nj/teg_onion_onion_common_data_nj-partition-156 / t_teg_onion_b_teg_onion_onion_common_data_nj_cg_onion_common_data_cos_svr_nj_001] Error reading entries at 9417597:1325183 : No such entry, Read Type Normal - Retrying to read in 54.075 seconds
10:55:11.454 [BookKeeperClientWorker-OrderedExecutor-61-0] ERROR org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed: L9417597 E1325183-E1325183, Sent to [9.150.226.98:3181, 9.150.228.32:3181], Heard from [] : bitset = {}, Error = 'No such entry'. First unread entry is (-1, rc = null)
```
**From the log, the two replica data are stored on two bookie nodes:**
9.150.226.98:3181, 9.150.228.32:3181

**Execute the commands on the two bookie nodes respectively:**
sh bin/bookkeeper shell ledger 9417597

Start with the reported PersistentDispatcherMultipleConsumers and PendingReadOp log entries, then inspect the BookKeeper ledger 9417597 using the mentioned `sh bin/bookkeeper shell ledger 9417597` command on both bookie nodes. Compare the `journalWriteData=false` configuration with the ledger state and determine why entry 1325183 is unavailable; done requires an identified cause and a confirmed corrective direction.

Written by the indexing model from the issue text.