[
https://issues.apache.org/jira/browse/KAFKA-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894207#comment-13894207
]
Neha Narkhede commented on KAFKA-1241:
--------------------------------------
Yes, it is a bug I hit during a test with large set of topics on the mirror
maker. However, due to absence of logging and the incomplete error message, it
is difficult to say what happened. Here is the rest of the stack trace -
java.lang.IllegalStateException: Attempt to begin a send operation with prior
send operation still in progress.
at kafka.common.network.Selector.poll(Selector.java:171)
at kafka.clients.producer.internals.Sender.run(Sender.java:137)
at kafka.clients.producer.internals.Sender.run(Sender.java:84)
at java.lang.Thread.run(Thread.java:619)
java.lang.IllegalStateException: Correlation id for response (7401215) does not
match request (7401214)
at kafka.clients.producer.internals.Sender.correlate(Sender.java:313)
at
kafka.clients.producer.internals.Sender.handleResponses(Sender.java:274)
at kafka.clients.producer.internals.Sender.run(Sender.java:144)
at kafka.clients.producer.internals.Sender.run(Sender.java:84)
at java.lang.Thread.run(Thread.java:619)
java.nio.BufferUnderflowException
at java.nio.Buffer.nextGetIndex(Buffer.java:480)
at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:336)
at kafka.common.protocol.types.Type$3.read(Type.java:88)
at kafka.common.protocol.types.Schema.read(Schema.java:50)
at kafka.common.protocol.types.ArrayOf.read(ArrayOf.java:30)
at kafka.common.protocol.types.Schema.read(Schema.java:50)
at kafka.common.protocol.types.ArrayOf.read(ArrayOf.java:30)
at kafka.common.protocol.types.Schema.read(Schema.java:50)
at
kafka.clients.producer.internals.Sender.handleResponses(Sender.java:273)
at kafka.clients.producer.internals.Sender.run(Sender.java:144)
at kafka.clients.producer.internals.Sender.run(Sender.java:84)
at java.lang.Thread.run(Thread.java:619)
> Cryptic serde error messages in new producer
> --------------------------------------------
>
> Key: KAFKA-1241
> URL: https://issues.apache.org/jira/browse/KAFKA-1241
> Project: Kafka
> Issue Type: Bug
> Components: producer
> Affects Versions: 0.9.0
> Reporter: Neha Narkhede
> Assignee: Jay Kreps
> Priority: Critical
> Attachments: KAFKA-1241.patch
>
>
> One of the motivations for the new serde format is better error reporting. I
> was running a test on the new mirror maker when I saw this exception -
> java.nio.BufferUnderflowException
> at java.nio.Buffer.nextGetIndex(Buffer.java:480)
> at java.nio.HeapByteBuffer.getInt(HeapByteBuffer.java:336)
> at kafka.common.protocol.types.Type$3.read(Type.java:88)
> at kafka.common.protocol.types.Schema.read(Schema.java:50)
> at kafka.common.protocol.types.ArrayOf.read(ArrayOf.java:30)
> at kafka.common.protocol.types.Schema.read(Schema.java:50)
> at kafka.common.protocol.types.ArrayOf.read(ArrayOf.java:30)
> at kafka.common.protocol.types.Schema.read(Schema.java:50)
> at
> kafka.clients.producer.internals.Sender.handleResponses(Sender.java:273)
> at kafka.clients.producer.internals.Sender.run(Sender.java:144)
> at kafka.clients.producer.internals.Sender.run(Sender.java:84)
> at java.lang.Thread.run(Thread.java:619)
> I was expecting to see a precise error message about the Request type that
> serde failed for. Instead it says Type$3 and no information on which field.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
