Why cursor.asyncReadEntriesOrWait() use topic.getMaxReadPosition()

[3286360470]

In org.apache.pulsar.broker.service.persistent.PersistentDispatcherMultipleConsumers#readMoreEntries()
There is a line of code：
cursor.asyncReadEntriesOrWait(messagesToRead, bytesToRead, this, ReadType.Normal, topic.getMaxReadPosition());

Thre're is one question is why the position returned by the topic.getMaxReadPosition() is returned from the TransactionBuffer instead of directly using the last add confirmed position of the ledger.

And the TransactionBuffer recover from the broker starting, But sometimes TransactionBufferRecover fails, causing the state to remain in the Initializing state, so it may cause broker dispach messages to consume blocked.