You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by gi...@git.apache.org on 2017/09/01 22:53:18 UTC
[GitHub] merlimat commented on issue #742: Avoid huge backlog on topic reloading: due to large gap between markDelete-offset and read-position of cursor.
merlimat commented on issue #742: Avoid huge backlog on topic reloading: due to large gap between markDelete-offset and read-position of cursor.
URL: https://github.com/apache/incubator-pulsar/issues/742#issuecomment-326699964
>Therefore, broker should notify to the client if distance between markDelete and readPosition reached to certain threshold. so, later on client will not face backlog and duplicate message delivery issue on topic unloading.
It's not just the gap. The described problem would only happen if there are many gaps in the acknowledgments, eg. consumer is acking every other message.
> Once, markDelete position advanced to expected threshold then broker again unblock subscriber and start delivering new messages.
We should already have that mechanism in place, right?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services