i will try to reproduce this problem later this week.
Bouncing the broker fixed the issue but the issue surfaced again after a
period of time. A little more context about this is that the cluster was
deployed to VMs and I discovered that the issue appeared whenever CPU wait
time was extremely
Hi ,
I want to update message content posted in kafka at particular offset?
is there any API available for it?
Thanks,
Snehalata
Hi,
The broker is healthy with no exceptions but the OffsetRequest
in getOffsetsBefore method fails with ClosedChannelException. This usually
happens after 2-3 hours of the app restart. I have looked at the code of
ConsumerOffsetChecker and I use the same logic. I do connect to the leader
to
Found it. SELinux was running on the box but not showing any events in the
audit log, however, the kernel log is another story entirely:
INFO: task java:4693 blocked for more than 120 seconds.
Not tainted 2.6.32-504.8.1.el6.x86_64 #1
echo 0 /proc/sys/kernel/hung_task_timeout_secs disables
Hi,
You cannot update message content after it has already been sent to Kafka.
One workaround would be using keyed messages, and send a new message with
the same key whenever you want to update the value correspondent to the
key. And turn on log compaction so that obsoleted messages with the
first,i increase some partitions for a topic,and is ok,
then i do kafka-reassign-partitions.sh ,and it speed long times to replicated
data,
and a partition status as partition: 68 leader: 5 replicas: 8,0,5,1
isr: 5,1
so i do kafka-preferred-replica-election.sh
