Re: Kafka broker not respecting log.roll.hours?

I don't know how Kafka's rollover algorithm is implemented, but this is common behavior for other logging frameworks. You would need a separate watcher/scheduled thread to rollover a log file, even if no events were coming in. Logback (and probably log4j, by the same author) dispenses with the watc

Encoder/Decoder exceptions

Are there any caveats to returning null from an Encoder or Decoder? I'm planning on doing this if there is a problem de/serializing a message, rather than throwing an exception.