-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.OutOfMemoryError: GC overhead limit exceeded' is observed when creating producers on a non-existent topic #6838
Comments
Fixes #6838 ### Motivation Close producer when the topic does not exists. ### Modifications 1. Fix exception handle for the topic does not exist. 2. Change state to Close when producer got TopicDoesNotExists exception so that the producer can close the cnx and will no longer add send timeout tasks to HashedWheelTimer.
Fixes #6838 ### Motivation Close producer when the topic does not exists. ### Modifications 1. Fix exception handle for the topic does not exist. 2. Change state to Close when producer got TopicDoesNotExists exception so that the producer can close the cnx and will no longer add send timeout tasks to HashedWheelTimer. (cherry picked from commit 6eed217)
Hi, we are consuming your 2.5.2 release we still observe this issue. PulsarProducerImp is hanging in the dump as reported previously. |
Fixes apache#6838 ### Motivation Close producer when the topic does not exists. ### Modifications 1. Fix exception handle for the topic does not exist. 2. Change state to Close when producer got TopicDoesNotExists exception so that the producer can close the cnx and will no longer add send timeout tasks to HashedWheelTimer.
@devprashantksinha Did you upgrade the Pulsar broker? #6879 makes some changes on the broker side. |
@codelipenghui : yes we have upgraded both client and pulsar chart components including broker to 2.5.2 . These are the steps I followed to reproduce :
Ideally, we should not see any ProducerImpl for a topic that doesn't exist. Right ? Please let me know if you need more info about the setup. |
…7120) Fixes #6838 related to #6879 ### Motivation Close producer without state check while the topic does not exists. The problem is the `State` of the producer failed to pass the check condition so that the producer can't be closed. If TopicDoesNotExsitsException happens on a producer, we can directly close this producer without state checking for the producer.
Fixes apache#6838 ### Motivation Close producer when the topic does not exists. ### Modifications 1. Fix exception handle for the topic does not exist. 2. Change state to Close when producer got TopicDoesNotExists exception so that the producer can close the cnx and will no longer add send timeout tasks to HashedWheelTimer. (cherry picked from commit 6eed217)
Fixes apache#6838 ### Motivation Close producer when the topic does not exists. ### Modifications 1. Fix exception handle for the topic does not exist. 2. Change state to Close when producer got TopicDoesNotExists exception so that the producer can close the cnx and will no longer add send timeout tasks to HashedWheelTimer.
…pache#7120) Fixes apache#6838 related to apache#6879 ### Motivation Close producer without state check while the topic does not exists. The problem is the `State` of the producer failed to pass the check condition so that the producer can't be closed. If TopicDoesNotExsitsException happens on a producer, we can directly close this producer without state checking for the producer.
Describe the bug
if we try to create producer for a non-existent topic the ProducerImpl object is hanging in the dump. Although producer creation fails but we see that ProducerImpl object corresponding to each producing action hanging in the dump. This behavior will lead to OOM in microservice which by mistake tries to produce consistently to a non-existent topic.
The text was updated successfully, but these errors were encountered: