-
Notifications
You must be signed in to change notification settings - Fork 261
Endless Kafka stacktraces when bad producer config #60
Comments
eager initialization: I am not sure if I remember correctly but the eager initialization is either really early (on the logger creation thread which may be the classloader thread which initializes But I agree, the config check should fail as soon as possible and only once. To fix this particular issue I'd however prefer the second option until we find a good abstraction for the producer lifecycle issues (see my comment on your PR). |
I also see endless stacktrace with bad producer config. Is there a way to restrict the no of retrials to a particular number? |
When the producer config is wrong, the createProducer raises an exception.
As this method is called by the LazyInitializer when a log arrives, each logs tries to create a producer, it fails and a stack trace is logged.
Prior to 0.2-RC1, the producer config check may have mitigated this issue.
Some solutions I can see:
The text was updated successfully, but these errors were encountered: