-Re: 0.72 Consumer: message is invalid, compression codec: NoCompressionCodec
Actually, looking at the code, the consumer client code can also catch this exception while iterating for messages. The fetcher thread inserts a special message before dying, which triggers an exception while client calls next message
So, we could create a new ConsumerConnector object when this error happens, which will re-initialize the fetcher threads.
On Feb 11, 2014, at 12:16 PM, vinh <[EMAIL PROTECTED]> wrote: