cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "daishi (JIRA)" <>
Subject [jira] Created: (CASSANDRA-136) Internal error processing get_columns_since
Date Tue, 05 May 2009 22:27:30 GMT
Internal error processing get_columns_since

                 Key: CASSANDRA-136
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: trunk
         Environment: Hudson build #59, accessing Cassandra via thrift/python
            Reporter: daishi

In a cluster configuration, I understand that data consistency/availability is on an "as things
propagate" basis.

However, I did not expect to see an actual exception thrown on a normal query using 'get_columns_since'.

I think the correct behavior when a node is unable to obtain the requested data is to simply
return less data
(in this case maybe an empty list?).

Client-side I saw:

...i/org/apache/cassandra/ in recv_get_columns_since(self)                   
    534       self._iprot.readMessageEnd()                                               
--> 535       raise x
    536     result = get_columns_since_result()                                          
TApplicationException: Internal error processing get_columns_since

and server-side I saw:

ERROR [pool-1-thread-1] 2009-05-05 18:04:21,781 (line 1106) Internal error
processing get_columns_since                         
java.lang.RuntimeException: java.util.concurrent.TimeoutException: Operation timed out.
        at org.apache.cassandra.service.StorageProxy.weakReadRemote(
        at org.apache.cassandra.service.StorageProxy.readProtocol(
        at org.apache.cassandra.service.CassandraServer.readColumnFamily(
        at org.apache.cassandra.service.CassandraServer.get_columns_since(
        at org.apache.cassandra.service.Cassandra$Processor$get_columns_since.process(
        at org.apache.cassandra.service.Cassandra$Processor.process(
        at org.apache.thrift.server.TThreadPoolServer$
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.util.concurrent.TimeoutException: Operation timed out.                   
        at org.apache.cassandra.service.StorageProxy.weakReadRemote(
        ... 9 more

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message