I'd
* verify you shutdown cleanly when restarting the broker
* test restarting the broker first before upgrading it (it may have been
sitting on a corrupt file for a long time and the issue is unrelated to the
upgrade)
re your questions:
1) probably not, unless it was caused by an unclean
Hi Bart,
This is a known issue discovered in version 1.1 -
https://issues.apache.org/jira/browse/KAFKA-7144
This issue has been fixed in Kafka Streams 2.0, any chance you can upgrade
to 2.0?
Thanks,
Bill
On Mon, Oct 8, 2018 at 2:46 PM Bart Vercammen wrote:
> Thanks John,
>
> I'll see what I
Thanks John,
I'll see what I can do regarding the logs ...
As a side not, our Kafka cluster is running version v1.1.1 in v0.10.2.1 log
format configuration (due to another issue: KAFKA-6000)
But, as said, I'll try to come up with some detailed logs, or a scenario to
reproduce this.
Greets,
Bart
Hi Bart,
I suspected it might not be feasible to just dump your production logs onto
the internet.
A repro would be even better, but I bet it wouldn't show up when you try
and reproduce it. Good luck!
If the repro doesn't turn out, maybe you could just extract the assignment
lines from your
Hi John,
Zipping up some logs from our running Kafka cluster is going to be a bit
difficult.
What I can do is try to reproduce this off-line and capture the logs from
there.
We also had a look in the PartitionAssignor source code (for 1.1.1) and
indeed this behaviour is a bit weird
as from the
Hi Bart,
This sounds a bit surprising. Is there any chance you can zip up some logs
so we can see the assignment protocol on the nodes?
Thanks,
-John
On Mon, Oct 8, 2018 at 4:32 AM Bart Vercammen wrote:
> Hi,
>
> I recently moved some KafkaStreams applications from v0.10.2.1 to v1.1.1
> and
Hey all,
Working on a tool for Kafka lifecycle management and one of the features
we're keen to try to wrap is user quotas.
This capability definitely exists through sets of scripts included with
Kafka, case and point: https://kafka.apache.org/documentation/#quotas
For context:
>
Dear community,
I updated my kafka cluster from version 1.1.0 to 2.0.0 according to the upgrade
guide for rolling upgrades today. I encountered a problem after starting the
new broker version. The log is full of
"Found a corrupted index file corresponding to log file
Hi Mike,
that sounds good! I've not yet received any other feedback, but worst case
scenario is that just the two of us discuss this over a cup of coffee :)
I'll talk to the Summit organizers again about some sort of venue and get
back to you once I know more. Maybe we can get a few more people
Hi,
I recently moved some KafkaStreams applications from v0.10.2.1 to v1.1.1
and now I notice a weird behaviour in the partition assignment.
When starting 4 instances of my Kafka Streams application (on v1.1.1) I see
that 17 of the 20 partitions (of a source topic) are assigned to 1 instance
of
10 matches
Mail list logo
