nodece commented on PR #25528:
URL: https://github.com/apache/pulsar/pull/25528#issuecomment-4257424554
@codelipenghui
The broker should not stop dispatching messages just because
`managedLedgerCursorPositionFlushSeconds` is higher.
In this implementation, `unackedMessages` is decremented when
`acknowledgeMessageAsync(...)` completes, and that completion is driven by the
managed cursor ack callback path, not by the periodic cursor flush task itself.
For the normal path, the ack immediately triggers async mark-delete/delete
persistence, so it does not wait for `managedLedgerCursorPositionFlushSeconds`.
`managedLedgerCursorPositionFlushSeconds` is only a fallback for
dirty/rate-limited cursor updates. In that case the cursor callback is
completed immediately and the actual flush is deferred, so dispatch is not
blocked waiting for that interval either.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
