You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "Ouriel (via GitHub)" <gi...@apache.org> on 2024/04/04 15:45:51 UTC
Re: [I] [Bug] version 2.8.0.7 Restarting broker consumes historical data [pulsar]
Ouriel commented on issue #20638:
URL: https://github.com/apache/pulsar/issues/20638#issuecomment-2037564434
Hello,
We are encountering the same behavior on our Pulsar cluster in 3.1.
It's a topic with long retention time (90 days) with delayed message that are acknowledged once consumed.
When restarting broker the pulsar backlog metric is getting back to the full backlog and we reprocess ~2M messages.
Here is a grafana screenshot after the broker restart showing `pulsar_subscription_back_log` metrics on the topic
If you have a workaround or a solution that will be great!
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org