-
Notifications
You must be signed in to change notification settings - Fork 340
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
Join request timeout doesn't consider rebalance_timeout #941
Labels
Comments
abicky
added a commit
to abicky/ruby-kafka
that referenced
this issue
May 17, 2022
This commit resolves zendesk#941. As the coorinator waits for each member to rejoin when rebalancing the group, the timeout of join request should be greater than rebalance_timeout. Otherwise, each member might send join requests over and over, and as a result, the following problems occur: * Some partitions are never processed until session_timeout passes * It takes much time for rebalance that occurs in a short time to finish
abicky
added a commit
to abicky/ruby-kafka
that referenced
this issue
May 17, 2022
This commit resolves zendesk#941. As the coorinator waits for each member to rejoin when rebalancing the group, the timeout of join request should be greater than rebalance_timeout. Otherwise, each member might send join requests over and over, and as a result, the following problems occur: * Some partitions are never processed until session_timeout passes * It takes much time for rebalance that occurs in a short time to finish
abicky
added a commit
to abicky/ruby-kafka
that referenced
this issue
May 17, 2022
This commit resolves zendesk#941. As the coorinator waits for each member to rejoin when rebalancing the group, the timeout of join request should be greater than rebalance_timeout. Otherwise, each member might send join requests over and over, and as a result, the following problems occur: * Some partitions are never processed until session_timeout passes * It takes much time for rebalance that occurs in a short time to finish
abicky
added a commit
to abicky/ruby-kafka
that referenced
this issue
May 17, 2022
This commit resolves zendesk#941. As the coorinator waits for each member to rejoin when rebalancing the group, the timeout of join request should be greater than rebalance_timeout. Otherwise, each member might send join requests over and over, and as a result, the following problems occur: * Some partitions are never processed until session_timeout passes * It takes much time for rebalance that occurs in a short time to finish
I've created the PR #943. |
abicky
added a commit
to abicky/ruby-kafka
that referenced
this issue
May 18, 2022
This commit resolves zendesk#941. As the coordinator waits for each member to rejoin when rebalancing the group, the timeout of join request should be greater than rebalance_timeout. Otherwise, each member might send join requests over and over, and as a result, the following problems occur: * Some partitions are never processed until session_timeout passes * It takes much time for rebalance that occurs in a short time to finish
abicky
added a commit
to abicky/ruby-kafka
that referenced
this issue
Jun 11, 2022
This commit resolves zendesk#941. As the coordinator waits for each member to rejoin when rebalancing the group, the timeout of join request should be greater than rebalance_timeout. Otherwise, each member might send join requests over and over, and as a result, the following problems occur: * Some partitions are never processed until session_timeout passes * It takes much time for rebalance that occurs in a short time to finish
Issue has been marked as stale due to a lack of activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Expected outcome
Join requests wait more than
rebalance_timeout
, and consumers don't resend join requests over and over as follows:Actually, the Java consumer waits
rebalance.timeout.ms
+ 5 seconds.cf. https://github.com/confluentinc/kafka/blob/c8fbe26f3bd3a7c018e7619deba002ee454208b9/clients/src/main/java/org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java#L568
The following sequence diagram describes the behavior:
Actual outcome
Join requests wait only
socket_timeout
, and consumers resend join requests over and over. As a result, it takes much time for the third consumer to join the consumer group as follows:The following sequence diagram describes the behavior:
The text was updated successfully, but these errors were encountered: