Hello All,
I am getting this error and I am not sure what that means. Specifically the
"Wrong request type 768"
[2013-11-04 16:56:47,540] ERROR Closing socket for /0:0:0:0:0:0:0:1 because
of error (kafka.network.Processor)
kafka.common.KafkaException: Wrong request type 768
at kafka.api.RequestKe
Hello all,
I am not sure if this is a Kafka issue, or an issue with the client that I
am using.
We have a fairly small setup, where everything sits on one server (Kafka
0.8, and Zookeeper). The message frequency is not too high (1-2 per second).
The setup works fine for a certain period of time
he.org/confluence/display/KAFKA/FAQ#FAQ-Whyaretheremanyrebalancesinmyconsumerlog%3F
>
> Also, what version of kafka 0.8 are you using? If not the beta, then
> what's the git hash?
>
> Joel
>
> On Thu, Nov 07, 2013 at 02:51:41PM -0500, Ahmed H. wrote:
> > Hello all,
&
again,
> logs would help.
>
> Also, you may want to try with the latest HEAD as opposed to the beta.
>
> Thanks,
>
> Joel
>
> On Fri, Nov 08, 2013 at 01:18:07PM -0500, Ahmed H. wrote:
> > Hello,
> >
> > I am using the beta right now.
> >
> > I
I have a basic Zookeeper/Kafka setup. I am still on Kafka 0.8 beta 1, and
Zookeeper 3.4.5. The activity on this machine isn't massive...I would say
the Kafka queues get a consistent 1 message every 2-3 seconds, as well as
occasional spikes, but still nothing large enough to push the limits. Both
Ka
Thanks,
>
> Jun
>
>
> On Wed, Jan 22, 2014 at 6:24 AM, Ahmed H. wrote:
>
> > I have a basic Zookeeper/Kafka setup. I am still on Kafka 0.8 beta 1, and
> > Zookeeper 3.4.5. The activity on this machine isn't massive...I would say
> > the Kafka queues get a consis
sion expiration, which were fixed
> in 3.3.4. Not sure if 3.4.5 exposes any new issues. The easiest thing is
> probably to avoid GC-induced ZK session timeout in the first place or use a
> larger session timeout.
>
> Thanks,
>
> Jun
>
>
> On Wed, Jan 22, 2014 at 8:29 A
Hello All,
I am seeing this issue very frequently when running a high volume of
messages through Kafka. It starts off well, and it can go on for minutes
that way, but eventually it reaches a point where the connection to Kafka
dies, then it reconnects and carries on. This repeats more frequently w
ns on the broker logs?
>
> Guozhang
>
>
> On Wed, Jun 25, 2014 at 7:47 AM, Ahmed H. wrote:
>
> > Hello All,
> >
> > I am seeing this issue very frequently when running a high volume of
> > messages through Kafka. It starts off well, and it can go on for minu
l data from client
> sessionid
> > 0x146958701700373, likely client has closed socket
> > at
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:220)
> > at
> >
> >
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
>
, Jun 25, 2014 at 6:02 PM, Neha Narkhede
wrote:
> If rebalance succeeded, then those error messages are harmless. Though I
> agree we shouldn't log those in the first place.
>
>
> On Wed, Jun 25, 2014 at 2:12 PM, Ahmed H. wrote:
>
> > Unfortunately I do not have the lo
11 matches
Mail list logo
