https://pulsar.apache.org/ logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
a
We unloaded a namespace, which moved the topics from one broker to another. In a certain topic, this caused a sudden increase in 
pulsar_subsctiption_back_log
by about 200,000 messages and the value is currently slowly decreasing. Simultaneously, the 
pulsar_subscription_unacked_messages
decreased from 55,000 to -83 and increased rapidly to 60,000 in a matter of seconds. Our inbound message rate stayed around 40 messages per second.
a
If it’s still relevant I can dig up in the code
a
@Asaf Mesika That would be very helpful, thanks!
a
Ok, I’m finding out.
Sorry - reading the code generated more questions that answers. I’ll get the replies and write you back here tomorrow when the bulk of the world resume working 🙂
@Yubiao Feng @Penghui Any idea? Amit - from I gathered from @Yubiao Feng both metric still have pending bugs. Some were fixed in recent versions, so for sure you need to be on the latest released version, but some have not been fixed. The code there is not written carefully in respect to data race and it needs some heavy refactoring.
y
• 
pulsar_subscription_unacked_messages
means the messages have been delivered to the client, but has not been acked
• 
pulsar_subscription_back_log
means how many messages should be acknowledged, contains delivered messages and not delivered
a
https://github.com/apache/pulsar-site/pull/721 @Yubiao Feng Can you double check me? This PR encodes your great response in the docs for future users
👀 1
y
Approved, Thanks 😘
Open in Slack
PreviousNext
Powered by