You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "kunwyoo (via GitHub)" <gi...@apache.org> on 2024/03/14 08:07:57 UTC
[D] Is there a way to disconnect a consumer based on it's backlog size? [pulsar]
GitHub user kunwyoo created a discussion: Is there a way to disconnect a consumer based on it's backlog size?
Suppose for some reason a consumer stopped processing the messages but didn't close its connection and its backlog is queueing up.
Is there a way for a broker to disconnect the lagging consumer based on the consumer's backlog size?
Or maybe if a threshold is reached, can the broker stop sending message to that specific consumer?
I thought the "receiver queue size" configuration for the consumer handled the latter scenario, but it seems like the configuration is not what I was looking for.
GitHub link: https://github.com/apache/pulsar/discussions/22265
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Is there a way to disconnect a consumer based on it's backlog size? [pulsar]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
GitHub user lhotari added a comment to the discussion: Is there a way to disconnect a consumer based on it's backlog size?
> Suppose for some reason a consumer stopped processing the messages but didn't close its connection and its backlog is queueing up.
>
> Is there a way for a broker to disconnect the lagging consumer based on the consumer's backlog size?
>
> Or maybe if a threshold is reached, can the broker stop sending message to that specific consumer?
@kunwyoo Thanks for sharing. This could be a useful feature. Is this pattern something that you have used with other messaging systems? Any references from good designs in this area?
GitHub link: https://github.com/apache/pulsar/discussions/22265#discussioncomment-8936971
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Is there a way to disconnect a consumer based on it's backlog size? [pulsar]
Posted by "kunwyoo (via GitHub)" <gi...@apache.org>.
GitHub user kunwyoo added a comment to the discussion: Is there a way to disconnect a consumer based on it's backlog size?
Nope. It's just a feature that I hope to be included.
GitHub link: https://github.com/apache/pulsar/discussions/22265#discussioncomment-8937450
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Is there a way to disconnect a consumer based on it's backlog size? [pulsar]
Posted by "sherlock-lin (via GitHub)" <gi...@apache.org>.
GitHub user sherlock-lin added a comment to the discussion: Is there a way to disconnect a consumer based on it's backlog size?
One question I have is whether disconnecting consumers if the messages are already backlogged will cause the backlog to increase
GitHub link: https://github.com/apache/pulsar/discussions/22265#discussioncomment-8922365
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org
Re: [D] Is there a way to disconnect a consumer based on it's backlog size? [pulsar]
Posted by "dao-jun (via GitHub)" <gi...@apache.org>.
GitHub user dao-jun added a comment to the discussion: Is there a way to disconnect a consumer based on it's backlog size?
From my understanding, NO
GitHub link: https://github.com/apache/pulsar/discussions/22265#discussioncomment-8924373
----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org