-
Notifications
You must be signed in to change notification settings - Fork 162
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
Tries to start consumer that is already started #286
Comments
Seems like it can get stuck in a loop where it does this indefinitely. It's hard for me to characterize further without reproducing but here is an error we see before it spins out trying to restart the existing consumer.
|
saw this again today. restarting elixir resolved it. Above it's one app in elixir (Elixir.MachineState.KafkaConsumer). Today it was another |
Are you still on 0.8.0, or have you moved to the latest? |
@jasongoodwin You may be interested to read/comment on #260 |
I'm using kafka 9+ (0.11 in prod) but maybe it's set incorrectly somewhere? Using the default config which appears to be 0.9.0 so don't think this is relevant. We've been running it for a while and it has only appeared a few times around restarts of the kafka consumer. |
I meant for KafkaEx, sorry @jasongoodwin |
Sorry for the slow reply - kafka_ex 0.8.2 I just remembered we're actually on a fork of 0.8.2 but I don't believe any of the changes would cause this - we added the ability to supply init params to gen consumers iirc. But it's another variable. It's just impossible to reproduce - it just periodically appears in running systems. We have 32 or so production servers running 24/7 and they are not common enough to cause users to notice any interruption but can occur for an hour at a time. Eg They seem to appear every minute or two for an hour and then stop in some recent observed incidents. Fork: I'll look at it and make sure it isn't a bug we introduced - if I'm the only one complaining about this I would be suspect of our fork but we also run it at a pretty big volume and we track every crash report we encounter. I'm sure that's different than how other people may be running it.
|
This sounds like a race condition, and a few of those were fixed in KafkaEx 0.8.3 when moving the heartbeat to a separate process. |
We see cases where KafkaEx tries to start a consumer that is already running for some reason. Looks pretty benign. I'm assuming this is internal to kafka_ex but let me know if I'm off here.
Started doing this after a crash observed in a genserver. Continues to throw these errors into the log.
We have a bug, but it seems to spin kafka_ex into this weird behaviour
Kafka_ex 0.8.0
The text was updated successfully, but these errors were encountered: