Overzealous logging?

Sorry for the crazy long log trace here (feel free to ignore this message :)) I'm just wondering if there's an easy way to sensibly reduce the amount of logging that a kafka produer (0.8) will emit if I try to send a message (with ack level 1), if no broker is currently running? This is from one

Re: Overzealous logging?

Agree that this is annoying. We plan to fix this largely as part of the Client Rewrite project. If you have ideas on fixing it before that, could you file a JIRA where we can start a discussion? Thanks, Neha On Mon, Sep 23, 2013

Re: Overzealous logging?

I'm wondering if a simple change could be to not log full stack traces for simple things like "Connection refused", etc. Seems it would be fine to just log the exception message in such cases. Also, the log levels could be tuned, such that things logged as ERROR indicate that all possible retries

Re: Overzealous logging?

This makes sense. Please file a JIRA where we can discuss a patch. Thanks, Neha On Tue, Sep 24, 2013 at 9:00 AM, Jason Rosenberg wrote: > I'm wondering if a simple change could be to not log full stack traces for > simple things like "Connection refused", etc. Seems it would be fine to > just

Re: Overzealous logging?

filed: https://issues.apache.org/jira/browse/KAFKA-1066 On Tue, Sep 24, 2013 at 12:04 PM, Neha Narkhede wrote: > This makes sense. Please file a JIRA where we can discuss a patch. > > Thanks, > Neha > > > On Tue, Sep 24, 2013 at 9:00 AM, Jason Rosenberg wrote: > > > I'm wondering if a simple ch