just conservatively treat both of them as fatal, causing
e.g. Streams embedded producers to be shutdown and restarted and hence
causing rebalances.
Guozhang
On Tue, Dec 21, 2021 at 7:07 AM Pieter Hameete
wrote:
> Hi all,
>
> After looking for an answer / some discussion on this matter
ons? Or how we could get more information on what's going on
here.
Best regards and thank you in advance!
Pieter Hameete
time for log loading
on startup
Hi Pieter,
Do the logs on the slow broker show a lot of "rebuilding corrupted indexes"
messages?
Cheers,
Liam Clarke-Hutchinson
On Tue, 9 Jun. 2020, 12:08 am Pieter Hameete,
wrote:
> Hello,
>
> we are observing Kafka brokers occasionally taki
an idea what could be causing this? Or any suggestions on
further tests to conduct to get closer to the cause?
Thank you in advance and have a good day!
-- Pieter Hameete
Van: Pieter Hameete
Verzonden: woensdag 20 november 2019 16:33
Aan: Ashutosh singh
CC: users@kafka.apache.org
Onderwerp: Re: Last Stable Offset (LSO) stuck for specific topic partition
after Broker issues
Hi Ashu, others,
I have tested with the latest kafkacat with librdkafka 1.2.2 which can
x27;s nothing I can do on the consumer side to get this
working again while keeping read mode read_committed.
Best,
Pieter
Van: Ashutosh singh
Verzonden: woensdag 20 november 2019 15:15
Aan: Pieter Hameete
CC: users@kafka.apache.org
Onderwerp: Re: Last Stable Offset
nd restart
the broker so that it will get in sync. Please make sure that you have
replica in-sync before deleting the partition.
Thanks
Ashu
On Wed, Nov 20, 2019 at 6:57 PM Pieter Hameete
wrote:
> Hello,
>
> after having some Broker issues (too many open files) we managed to
> re
Hello,
after having some Broker issues (too many open files) we managed to recover our
Brokers, but read_committed consumers are stuck for a specific topic partition.
It seems like the LSO is stuck at a specific offset. The transactional producer
for the topic partition is working without error
: Re: Repeating UNKNOWN_PRODUCER_ID errors for Kafka streams
applications
Hello Pieter,
Please feel free to apply this two-liner to your branch and see if it
helps: https://github.com/apache/kafka/pull/6951
Guozhang
On Thu, Jun 13, 2019 at 12:30 AM Pieter Hameete
wrote:
> Hi Guozhang,
>
ix if you're willing to do the former.
Guozhang
On Wed, Jun 12, 2019 at 4:13 AM Pieter Hameete
wrote:
> Hey Jonathan,
>
> Thanks for the input. We've looked into the issue you linked but
> changing the topic config didn’t work for us (see earlier mails in this
> thread
On Tue, Jun 11, 2019 at 11:04 AM Pieter Hameete
wrote:
> Hi Guozhang,
>
> Thanks that clarifies a lot. The segment size or segment ms is not the
> issue here then, changing these properties does not make the errors go
> away either 😊
>
> Regarding the proposed solutions:
&
e your commit interval, and hence reduce the delete-records
frequency, or 2) decrease your num.partitions so that the per-partition traffic
from a single producer can be reasonably large.
Guozhang
On Fri, Jun 7, 2019 at 2:09 AM Pieter Hameete
wrote:
> Hi Guozhang,
>
> I've che
00015-repartition-xx
partitions? If it is too frequent that would cause the producer ID stored on
brokers to be removed too early and therefore UNKNOWN_PRODUCER_ID, but
overriding the segment size / ms should prevent it from being triggered too
often.
Guozhang
On Thu, Jun 6, 2019 at 5:10 AM Pieter Hame
https://cwiki.apache.org/confluence/display/KAFKA/KIP-360%3A+Improve+handling+of+unknown+producer
could solve what we are seeing here?
Best,
Pieter
-Oorspronkelijk bericht-
Van: Pieter Hameete
Verzonden: Thursday, 6 June 2019 13:39
Aan: users@kafka.apache.org
Onderwerp: RE: Repeating
will take one
offset as well.
Your overridden configs look good to me, and it's indeed weird why it did not
mitigate your observed issue. Which Kafka version did you use?
Guozhang
On Wed, Jun 5, 2019 at 4:43 AM Pieter Hameete
wrote:
> Hi Guozhang,
>
> Some additional finding:
Hi Guozhang,
Some additional finding: it seems to only happen on Kakfa Streams repartition
topics. We haven't seen this happening for any other topics so far.
Best,
Pieter
-Oorspronkelijk bericht-
Van: Pieter Hameete
Verzonden: Wednesday, 5 June 2019 11:23
Aan:
igs in the repartition
topics?
Guozhang
On Tue, Jun 4, 2019 at 2:10 AM Pieter Hameete
wrote:
> Hello,
>
> Our Kafka streams applications are showing the following warning every
> few seconds (on each of our 3 brokers, and on each of the 2 instances
> of the streams application):
Hello,
Our Kafka streams applications are showing the following warning every few
seconds (on each of our 3 brokers, and on each of the 2 instances of the
streams application):
[Producer
clientId=event-rule-engine-dd71ae9b-523c-425d-a7c0-c62993315b30-StreamThread-1-1_24-producer,
transaction
Hello,
Our Kafka streams applications are showing the following warning every few
seconds (on each of our 3 brokers, and on each of the 2 instances of the
streams application):
[Producer
clientId=event-rule-engine-dd71ae9b-523c-425d-a7c0-c62993315b30-StreamThread-1-1_24-producer,
transaction
19 matches
Mail list logo
