Hi Damian,
Thanks for running the release.
I tried building from source and running the quick start on Linux &
Windows with both Java 8 & 9.
Here's the result:
+-+-+-+
| | Linux | Windows |
+ +-+-+
|
Hello,
We recently tried doing a rolling upgrade from 0.9.0 to 1.0.0. We had
upgraded 2 brokers when we began seeing decode errors with our python
client in boto3 trying to decode ProduceRequest_v2. But other than a large
spew of error messages, we were still consuming and producing normally.
When
Matthias,
Thank you for the quick response. I was able to verify that was the
problem. I had seen similar solutions but thought that the expiration would
not happen with an active consumer group (but it makes sense considering it
is just another topic). I appreciate the help and timely response ve
Jordon,
not sure, if this applies to your situation, but brokers only maintain
committed offsets for 24h by default. This offset-retention time is
applied for each partitions individually and starts when the commit was
done (ie, offset can expired even if the consumer group is active).
Thus, if y
Hello,
I am seeing an issue where I have a single streams app running (so a
consumer group of one) that is subscribed to about 10 topics. If the
streams app gets killed and restarted, many of the offsets for the consumer
group are reset to 0 and a lot of data is unintentionally reprocessed. The
of
Is It recommended to move to 1.0 release if we want to overcome this issue
? Please advise, Ted.
Thanks.
R
On Thu, Mar 15, 2018 at 7:43 PM, Ted Yu wrote:
> Looking at KAFKA-3702, it is still Open.
>
> FYI
>
> On Thu, Mar 15, 2018 at 5:51 PM, Raghav wrote:
>
> > I am hitting this issue possibl
