Hi Aravind,
The tagged versions may not be released yet, we just tag them when the
corresponding fix commit is merged to the branch (e.g. 1.1.x, 2.0.x, etc).
The next release that will include this commit is 2.1.0, whose feature
freeze date is today:
Thanks Guozhang, Yes we are hitting the same issue.
I see in that ticket that it’s fixed in 1.1.2, 2.0.1, 2.1.0, but I don’t see
those versions in here https://kafka.apache.org/downloads on the Kafka download
page. How can we get access to any of these versions?
Thanks
Aravind
> On Sep
Could you take a look at https://issues.apache.org/jira/browse/KAFKA-7284
and see if you are hitting this?
Guozhang
On Fri, Sep 28, 2018 at 5:22 PM, Aravind Dongara wrote:
> Hi Guozhang
>
> Thanks for your reply.
> We are using Kafka 1.1.1
>
> Thanks
> Aravind
>
>
> > On Sep 28, 2018, at 4:45
Hi Guozhang
Thanks for your reply.
We are using Kafka 1.1.1
Thanks
Aravind
> On Sep 28, 2018, at 4:45 PM, Guozhang Wang wrote:
>
> Hello Aravind,
>
> Which version of Kafka are you currently using? What you described seems to
> be fixed in the latest version already, so I want to check if
Hello Aravind,
Which version of Kafka are you currently using? What you described seems to
be fixed in the latest version already, so I want to check if you are using
an older version and if yes, what's the best way to work around it.
Guozhang
On Thu, Sep 27, 2018 at 12:54 PM, Aravind Dongara
During a rebalance triggered by kafka-coordinator-heartbeat-thread losing
connection to ‘Group coordinator’, we noticed that a stream thread is shutting
down when it catches a ProducerFencedExcpetion while flushing the state store.
This also causes the stream-state on that node to be stuck in
