Skip to content
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

Consumer Group has no response (rebalance notified) for added partition during runtime while producer is ok #1237

Closed
PoacherBro opened this issue Dec 16, 2018 · 4 comments

Comments

@PoacherBro
Copy link

PoacherBro commented Dec 16, 2018

Versions

Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.
Sarama Version: 1.19.0
Kafka Version: 1.1.0
Go Version: 1.11.2

Configuration

What configuration values are you using for Sarama and Kafka?

  • Kafka is default setting, no change
  • Sarama: use ConsumerGroup API, specify oldest kafka version is 0.10.2, metadata refresh frequency is 1 minute, offset initial is OffsetNewest.

For detail code, you can refer to consumer_group_test.go.

Logs

When filing an issue please provide logs from Sarama and Kafka if at all
possible. You can set sarama.Logger to a log.Logger to capture Sarama debug
output.

// Consumer Group log
[sarama] 2018/12/16 21:52:27 client/metadata fetching metadata for all topics from broker localhost:9092
.......  // still consumer the message pre-created partition
// Producer log
2018/12/16 producer_test.go:52: Pushed value: key[leo]-value[20181216215131]
[sarama] 2018/12/16 21:51:31 producer/broker/1 state change to [open] on test1/2
2018/12/16 producer_test.go:52: Pushed value: key[leo]-value[20181216215134]
[sarama] 2018/12/16 21:51:34 producer/broker/1 state change to [open] on test1/1
Problem Description

When add new partitions (from 1 to 3), producer can refreshed and send new message to added partitions, but for consumer group, it has no response (rebalance notification) until I start-up a new consumer in a same consumer group.

@chenhengqi
Copy link

Any updates on this issue ? I also experienced this problem.

@clhongooo
Copy link

Any updates on this issue ? I also experienced this problem.

+1

@antsbean
Copy link
Contributor

antsbean commented Oct 30, 2019

pr #1525 had fixed this problem

@PoacherBro
Copy link
Author

See the fix, closed this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants