There's a log message that
i receive and than application terminates stating that there's still some
message left in the queue.
I have tried all the parameters that i could, like increasing the buffer size,
linger.ms<http://linger.ms/> but to no avail I wasnt able to solve this
0.11 what is the expected behaviour? Will the upgraded
Yes
broker node join the cluster? Will the cluster work as expected? Is 0.11
Yes
inter broker protocol and log message format backward compatible with
0.10.0 ?
Yes. But with a performance penalty on the Kafka server because each
okers.
Can some one let me know if I just update the binaries in one of the broker
in a Kafka cluster 0.11 what is the expected behaviour? Will the upgraded
broker node join the cluster? Will the cluster work as expected? Is 0.11
inter broker protocol and log message format backward compatible
72 ERROR kafka.server.ReplicaManager
>> 2017-12-15T07:39:40.381+ [ReplicaManager broker=1] Error processing
>> fetch operation on partition __consumer_offsets-1 offset 2045483676
>> kafka-request-handler-5 74 ERROR kafka.server.ReplicaManager
>> 2017-12-15T07:39:4
_consumer_offsets-31 offset 235294887
>
> Every second or so.
>
> If we stop that broker, those errors simply shift to the next leader for
> those 4 partitions. And moving the partitions to completely new brokers
> just moves the errors.
>
> We only see this on kafka1. not
, those errors simply shift to the next leader for
those 4 partitions. And moving the partitions to completely new brokers
just moves the errors.
We only see this on kafka1. not the other 9 brokers which had the log
message fromat upgraded a day or two later.
Any suggestion on how to proceed? I'
Dear all,
I am aware of the fact that Kafka is pull based, however, I’ve been curious: is
it possible to modify a message between consumer fetch request and before the
message queues up at the consumer side?
Thanks in advance,
Dominik
s it possibile to log message header / key into server logs ( Log4j ) on
> message broker ?
> I would like to track message after a few years , so I need to prove that
> message exists on message broker in some particular time.
>
> my case :
>
> Publisher log information
Hi
Is it possibile to log message header / key into server logs ( Log4j ) on
message broker ?
I would like to track message after a few years , so I need to prove that
message exists on message broker in some particular time.
my case :
Publisher log information into business log (e.g. log4j
the last message on the partition. Now the questions are:
> > > 1. If the consumer tries to fetch next message, then what value
> > > will be return by Kafka server to consumer for offset ?
> > >
> > > 2. If I want my consumer to wait till producer sends next log
> > > message then how can I achieve this ? How can I make my consumer to
> wait
> > > for next message ?
> > >
> > >
> > > - Ganesh
> > >
> >
>
sumer for offset ?
> >
> > 2. If I want my consumer to wait till producer sends next log
> > message then how can I achieve this ? How can I make my consumer to wait
> > for next message ?
> >
> >
> > - Ganesh
> >
>
; the last message on the partition. Now the questions are:
> 1. If the consumer tries to fetch next message, then what value
> will be return by Kafka server to consumer for offset ?
>
> 2. If I want my consumer to wait till producer sends next log
> message then how ca
to
the last message on the partition. Now the questions are:
1. If the consumer tries to fetch next message, then what value
will be return by Kafka server to consumer for offset ?
2. If I want my consumer to wait till producer sends next log
message then how can I achieve this ? How
13 matches
Mail list logo
