Re: Kafka broker error from samza producer
I forgot to mention that for me the error always happened after restarting a broker. Sent from my iPhone On Jul 23, 2015, at 4:25 PM, Jordan Shaw jor...@pubnub.com wrote: Hey Roger, I restarted the producer and the error went away on the broker. If it comes back I'll switch over to lz4. Thanks for the reply. -Jordan On Thu, Jul 23, 2015 at 9:32 AM, Roger Hoover roger.hoo...@gmail.com wrote: Hi Jordan, I ran into a similiar issue when using snappy compression and the new producer. If you disable compression or switch to lz4 or gzip, does the issue go away? Cheers, Roger On Wed, Jul 22, 2015 at 11:54 PM, Jordan Shaw jor...@pubnub.com wrote: Hey Everyone, I'm getting an: kafka.message.InvalidMessageException: Message found with corrupt size (0) in my kafka server.log here is the full stack trace: https://gist.github.com/jshaw86/516cf47b6fd7559e7dc1. It indicates that the error is caused by a bad produce call from the samza producer any idea what could be causing this? Just about the only thing that I can find is maybe a issue with snappy or compression but I don't see a snappy call in the traceback. -- Jordan Shaw Full Stack Software Engineer PubNub Inc -- Jordan Shaw Full Stack Software Engineer PubNub Inc 1045 17th St San Francisco, CA 94107
Re: Kafka broker error from samza producer
Hey Roger, I restarted the producer and the error went away on the broker. If it comes back I'll switch over to lz4. Thanks for the reply. -Jordan On Thu, Jul 23, 2015 at 9:32 AM, Roger Hoover roger.hoo...@gmail.com wrote: Hi Jordan, I ran into a similiar issue when using snappy compression and the new producer. If you disable compression or switch to lz4 or gzip, does the issue go away? Cheers, Roger On Wed, Jul 22, 2015 at 11:54 PM, Jordan Shaw jor...@pubnub.com wrote: Hey Everyone, I'm getting an: kafka.message.InvalidMessageException: Message found with corrupt size (0) in my kafka server.log here is the full stack trace: https://gist.github.com/jshaw86/516cf47b6fd7559e7dc1. It indicates that the error is caused by a bad produce call from the samza producer any idea what could be causing this? Just about the only thing that I can find is maybe a issue with snappy or compression but I don't see a snappy call in the traceback. -- Jordan Shaw Full Stack Software Engineer PubNub Inc -- Jordan Shaw Full Stack Software Engineer PubNub Inc 1045 17th St San Francisco, CA 94107
Re: Kafka broker error from samza producer
Hi Jordan, I ran into a similiar issue when using snappy compression and the new producer. If you disable compression or switch to lz4 or gzip, does the issue go away? Cheers, Roger On Wed, Jul 22, 2015 at 11:54 PM, Jordan Shaw jor...@pubnub.com wrote: Hey Everyone, I'm getting an: kafka.message.InvalidMessageException: Message found with corrupt size (0) in my kafka server.log here is the full stack trace: https://gist.github.com/jshaw86/516cf47b6fd7559e7dc1. It indicates that the error is caused by a bad produce call from the samza producer any idea what could be causing this? Just about the only thing that I can find is maybe a issue with snappy or compression but I don't see a snappy call in the traceback. -- Jordan Shaw Full Stack Software Engineer PubNub Inc
Kafka broker error from samza producer
Hey Everyone, I'm getting an: kafka.message.InvalidMessageException: Message found with corrupt size (0) in my kafka server.log here is the full stack trace: https://gist.github.com/jshaw86/516cf47b6fd7559e7dc1. It indicates that the error is caused by a bad produce call from the samza producer any idea what could be causing this? Just about the only thing that I can find is maybe a issue with snappy or compression but I don't see a snappy call in the traceback. -- Jordan Shaw Full Stack Software Engineer PubNub Inc
