michalcukierman commented on issue #23239: URL: https://github.com/apache/pulsar/issues/23239#issuecomment-2327272418
With this code, shouldn't the last message be re-delivered to the client after the subscription is created? With the code I've provided the backlog "hangs" and no message is delivered to the consumer. So now I see two issues: - the backlog is incorrect - the message from the backlog is not re-delivered to the customer, even if there is a code that rewinds the position one entry backward. Have in mind that there may be implications of the incorrect backlog: - some services may rely on the backlog to scale up/down (i.e. Keda) - alerting rules may be fired if the backlog is not empty for a long time - people may get confused and spend a lot of time looking for errors -- 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]
