zjxxzjwang commented on PR #25010:
URL: https://github.com/apache/pulsar/pull/25010#issuecomment-3771859893
> > Currently, Pulsar Broker lacks a metric to track instances where delayed
messages exceed their TTL. This results in messages set with delayed delivery
times exceeding the TTL expiring before being consumed by users, with no
mechanism to detect this occurrence. Consequently, there is a significant risk
of message loss.
>
> The implementation doesn't seem to match the goal of the change ("track
instances where delayed messages exceed their TTL"). It currently target the
case where the message has already been expired when it gets published. How
common is that case? What TTL value are you using?
I have made the necessary modifications, and the current logic will not
introduce additional overhead. Based on extensive user usage patterns, this
counter is critical and highly valuable. Without it, users would remain unaware
when messages expire due to delayed delivery exceeding the TTL. With this
counter in place, we can implement alerting mechanisms to notify users and
adjust the TTL accordingly.
--
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]
