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

Some Kafka consumers become idle after some Kafka nodes restart #41

Open
GenTang opened this issue Jun 24, 2020 · 0 comments
Open

Some Kafka consumers become idle after some Kafka nodes restart #41

GenTang opened this issue Jun 24, 2020 · 0 comments
Assignees
Labels
bug Something isn't working P2 Priority 2 (High)

Comments

@GenTang
Copy link
Contributor

GenTang commented Jun 24, 2020

Bug Report

When some nodes of Kafka restart, some Kafka consumers in Ligase become idle, not consume any messages.

If we check Kafka by kafka-consumer-groups --bootstrap-server localhost:9093 --describe --all-groups, there are some groups that has no consumer-id for some topic.

1. Minimal reproduce step (Required)

  • Create some Kafka topics and send messages to these topics
  • Consume these topics as the way of Ligase (Extract the Kafka consume code)
  • Restart Kafka node several times

2. What did you expect to see? (Required)

Consumer continue consuming message

3. What did you see instead (Required)

Consumer become idle and does not consume message and no error is raised.
Or restart consumer service.

4. Root Cause Analysis

It seems that this bug is related to this sdk bug

@GenTang GenTang added bug Something isn't working P1 Priority 1 (Urgent) labels Jun 24, 2020
@GenTang GenTang added P2 Priority 2 (High) and removed P1 Priority 1 (Urgent) labels Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P2 Priority 2 (High)
Projects
None yet
Development

No branches or pull requests

2 participants