You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "graham sanderson (JIRA)" <ji...@apache.org> on 2014/09/05 21:24:28 UTC
[jira] [Comment Edited] (CASSANDRA-7849) Server logged error
messages (in binary protocol) for unexpected exceptions could be more
helpful
[ https://issues.apache.org/jira/browse/CASSANDRA-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123425#comment-14123425 ]
graham sanderson edited comment on CASSANDRA-7849 at 9/5/14 7:23 PM:
---------------------------------------------------------------------
Certainly a "connection reset by peer" or a "connection timed out" don't count as server errors, and there was a similar discussion on CASSANDRA-6424 about not really being able to tell what is a _real_ error vs something inconsequential.
I will say that these server logs are useful, for detecting bugs in client drivers (we use several), application bugs (unclean shutdowns, incorrect pooling etc), as well as more subtle things (we discovered today, that through a chain of distributed configs, some service in beta was pulling data from production cassandra).
Therefore my vote would be to change this to INFO, and add the additional logging as per the patch.
was (Author: graham sanderson):
Certainly a "connection reset by peer" or a "connection reset" don't count as server errors, and there was a similar discussion on CASSANDRA-6424 about not really being able to tell what is a _real_ error vs something inconsequential.
I will say that these server logs are useful, for detecting bugs in client drivers (we use several), application bugs (unclean shutdowns, incorrect pooling etc), as well as more subtle things (we discovered today, that through a chain of distributed configs, some service in beta was pulling data from production cassandra).
Therefore my vote would be to change this to INFO, and add the additional logging as per the patch.
> Server logged error messages (in binary protocol) for unexpected exceptions could be more helpful
> -------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7849
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7849
> Project: Cassandra
> Issue Type: Improvement
> Reporter: graham sanderson
> Fix For: 1.2.19, 2.0.11, 2.1.0
>
> Attachments: cassandra-1.2-7849.txt
>
>
> From time to time (actually quite frequently) we get error messages in the server logs like this
> {code}
> ERROR [Native-Transport-Requests:288] 2014-08-29 04:48:07,118 ErrorMessage.java (line 222) Unexpected exception during request
> java.io.IOException: Connection reset by peer
> at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> at sun.nio.ch.IOUtil.read(IOUtil.java:192)
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64)
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> These particular cases are almost certainly problems with the client driver, client machine, client process, however after the fact this particular exception is practically impossible to debug because there is no indication in the underlying JVM/netty exception of who the peer was. I should note we have lots of different types of applications running against the cluster so it is very hard to correlate these to anything
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)