[ https://issues.apache.org/jira/browse/CASSANDRA-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004593#comment-13004593 ]
Shotaro Kamio commented on CASSANDRA-2282: ------------------------------------------ I'm trying to find out when the timeout happens. So, I put logging to CassandraServer.java and ReadCallback.java just before timeout exception. I saw Timeout occurs even when 2 responses are received for query with quorum. 2 responses should be enough for quorum. Is it correct behavior? ------ INFO [pool-1-thread-44] 2011-03-09 23:34:47,685 ReadCallback.java (line 125) Operation timed out - received only 2 responses from /xx.xx.xx.67, /xx.xx.xx.68, command class = org.apache.cassandra.db.SliceFromReadCommand INFO [pool-1-thread-44] 2011-03-09 23:34:47,686 CassandraServer.java (line 110) --- timed out: Operation timed out - received only 2 responses from /xx.xx.xx.67, /xx.xx.xx.68, . ----- > ReadCallback AssertionError: resolver.getMessageCount() <= endpoints.size() > --------------------------------------------------------------------------- > > Key: CASSANDRA-2282 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2282 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 0.7.3 > Reporter: Tyler Hobbs > Assignee: Jonathan Ellis > Attachments: 2282-v2.txt, 2282.txt > > > In a three node cluster with RF=2, when trying to page through all rows with > get_range_slices() at CL.ONE, I get timeouts on the client side. Looking at > the Cassandra logs, all of the nodes show the following AssertionError > repeatedly: > {noformat} > ERROR [RequestResponseStage:2] 2011-03-07 19:10:27,527 > DebuggableThreadPoolExecutor.java (line 103) Error in ThreadPoolExecutor > java.lang.AssertionError > at > org.apache.cassandra.service.ReadCallback.response(ReadCallback.java:127) > at > org.apache.cassandra.net.ResponseVerbHandler.doVerb(ResponseVerbHandler.java:49) > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:72) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > ERROR [RequestResponseStage:2] 2011-03-07 19:10:27,529 > AbstractCassandraDaemon.java (line 114) Fatal exception in thread > Thread[RequestResponseStage:2,5,main] > java.lang.AssertionError > at > org.apache.cassandra.service.ReadCallback.response(ReadCallback.java:127) > at > org.apache.cassandra.net.ResponseVerbHandler.doVerb(ResponseVerbHandler.java:49) > at > org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:72) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:636) > {noformat} > The nodes are all running 0.7.3. The cluster was at size 3 before any data > was inserted, and everything else appears perfectly healthy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira