The request log will show the total time that a broker takes to complete a
request. Could you see if that request takes more then request timeout to
complete?
Thanks,
Jun
On Wed, May 28, 2014 at 2:18 PM, Maung Than wrote:
> No.
>
> Now we only have this exception in the terminal: It seems to
No.
Now we only have this exception in the terminal: It seems to be happening with
gzip or large volume of sends even without compression:
java.net.SocketTimeoutException
at
sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:201)
at sun.nio.ch.ChannelInputStrea
Do you see any exceptions on the broker side request logs and server logs?
Guozhang
On Wed, May 28, 2014 at 12:25 PM, Maung Than wrote:
> The new value is 25000 ms.
> We still have the same issue.
>
> Thanks,
> Maung
>
> On May 27, 2014, at 3:15 PM, Guozhang Wang wrote:
>
> > What is the new
The new value is 25000 ms.
We still have the same issue.
Thanks,
Maung
On May 27, 2014, at 3:15 PM, Guozhang Wang wrote:
> What is the new value you set? The new exception you saw seems not related
> to Kafka network issues, you may want to, for example, check
>
> https://netbeans.org/bugzil
What is the new value you set? The new exception you saw seems not related
to Kafka network issues, you may want to, for example, check
https://netbeans.org/bugzilla/show_bug.cgi?id=14
On Tue, May 27, 2014 at 12:34 PM, Maung Than wrote:
> We are now getting additional IO exception as well
We are now getting additional IO exception as well:
May 27, 2014 12:32:29 PM sun.rmi.transport.tcp.TCPTransport$AcceptLoop
executeAcceptLoop
WARNING: RMI TCP Accept-0: accept loop for
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=50110] throws
java.io.IOException: The server sockets create
You meant to say the below parameter; if so we do not override it; so it is the
default 10 sec. Should It be larger? It is happening only with Gzip; Snappy or
no compression works fine.
request.timeout.ms 1 The amount of time the broker will wait trying
to meet the request.required.
I think Guozhang meant to say request.timeout.ms, not session timeout. You
can try increasing the request timeout through the request-timeout-ms
command line option.
Thanks,
Neha
On Tue, May 27, 2014 at 8:55 AM, Guozhang Wang wrote:
> Maung,
>
> This issue may be due to the session timeout va
Maung,
This issue may be due to the session timeout value set too small. With
batch size 1000 and message size 420 you are sending 420K of data in each
request. What is your time out value?
Guozhang
On Mon, May 26, 2014 at 11:46 PM, Maung Than wrote:
> Hi All,
>
> This is what we are running
Hi All,
This is what we are running on the Broker:
/Users/worun/kafkabuild/kafka-0.8.1-src/bin/kafka-producer-perf-test.sh
--broker-list vp21q12ic-hpaj020921:9092 --messages 1000 --topic imessage
--threads 10 --message-size 420 --batch-size 1000 --compression-codec 1
We are getting the b
10 matches
Mail list logo
