Hi Guozhang, I will talk to the team about prioritizing the recreation of this
scenario and gathering logs.
- Eric
> On Nov 5, 2017, at 9:39 AM, Guozhang Wang wrote:
>
> Hello Laven / Eric,
>
> I personally cannot think of any more bug fixes than KAFKA-5152 that is
> trying to solve a relativ
Hello Laven / Eric,
I personally cannot think of any more bug fixes than KAFKA-5152 that is
trying to solve a relative issue, and we would love to know what did you
observe that in 0.11.0.1 this issue still exists: i.e. the first instance
is stuck with the rebalance state, as we have moved the res
Streams is backward compatible from 0.10.1 on.
So 1.0.0 does not work with 0.10.0 but 0.10.1, 0.10.2, and 0.11.0.
Compare:
https://docs.confluent.io/current/streams/upgrade-guide.html#compatibility
-Matthias
On 10/25/17 7:54 AM, Eric Lalonde wrote:
>
>> On Oct 24, 2017, at 8:53 PM, Matthias J
> On Oct 24, 2017, at 8:53 PM, Matthias J. Sax wrote:
>
> Might be worth a try with 1.0.0 RC3 -- even if I doubt that much changes.
>
> Can you provide debug logs for your Kafka streams applications as well
> as brokers? This would help to dig into this.
>
I searched, but it wasn’t clear to m
Might be worth a try with 1.0.0 RC3 -- even if I doubt that much changes.
Can you provide debug logs for your Kafka streams applications as well
as brokers? This would help to dig into this.
-Matthias
On 10/24/17 5:53 PM, Ted Yu wrote:
> Eric:
> I wonder if it is possible to load up 1.0.0 RC3 o
Eric:
I wonder if it is possible to load up 1.0.0 RC3 on test cluster and see
what the new behavior is ?
Thanks
On Tue, Oct 24, 2017 at 5:41 PM, Eric Lalonde wrote:
>
> >>> Could it be, that the first KafkaStreams instance was still in status
> >>> "rebalancing" when you started the second/thir
>>> Could it be, that the first KafkaStreams instance was still in status
>>> "rebalancing" when you started the second/third container? If yes, this
>>> might explain what you observed: if the first instance is in status
>>> "rebalancing" it would miss that new instanced are joining the group.
>>
We had multiple Jira. I guess this one is the fix you are looking for:
https://issues.apache.org/jira/browse/KAFKA-5152
-Matthias
On 10/24/17 3:21 PM, Eric Lalonde wrote:
>>
>> Could it be, that the first KafkaStreams instance was still in status
>> "rebalancing" when you started the second/thir
>
> Could it be, that the first KafkaStreams instance was still in status
> "rebalancing" when you started the second/third container? If yes, this
> might explain what you observed: if the first instance is in status
> "rebalancing" it would miss that new instanced are joining the group.
> (We fi
Hi,
the issue you describe, that on a "fresh" restart, all tasks are
assigned to the first thread is known, and the solution for it was to
introduce the new broker config you mentioned. Thus, there is no config
for 0.10.2.x brokers or Streams API to handle this case (that's why we
introduced the n
Hi all,
We're upgrading a Kafka streams application from 0.10.2.1 to 0.11.0.1 and
our application is running against a Kafka cluster with version 0.10.2.1.
When we first attempted to upgrade our application to Kafka 0.11.0.1, we
observed that when we deleted the PVCs for the service, and restarte
11 matches
Mail list logo
