cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gabriele renzi <>
Subject Re: timeout while running simple hadoop job
Date Wed, 12 May 2010 10:11:03 GMT
a follow up for anyone that may end up on this conversation again:

I kept trying and neither changing the number of concurrent map tasks,
nor the slice size helped.
Finally, I found out a screw up in our logging system,  which had
forbidden us from noticing a couple of recurring errors in the logs :

ERROR [ROW-READ-STAGE:1] 2010-05-11 16:43:32,328 (line 101) Error in
java.lang.RuntimeException: java.lang.RuntimeException: corrupt sstable
        at org.apache.cassandra.service.RangeSliceVerbHandler.doVerb(
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.RuntimeException: corrupt sstable
        at org.apache.cassandra.db.ColumnFamilyStore.getKeyRange(
        at org.apache.cassandra.db.ColumnFamilyStore.getRangeSlice(
        at org.apache.cassandra.service.RangeSliceVerbHandler.doVerb(
        ... 4 more
Caused by:
/path/to/data/Keyspace/CF-123-Index.db (Too many open files)
        at Method)
        ... 7 more

and the related

 WARN [main] 2010-05-11 16:43:38,076 (line 190)
Transport error occurred during acceptance of message.
org.apache.thrift.transport.TTransportException: Too many open files
        at org.apache.thrift.transport.TServerSocket.acceptImpl(
        at org.apache.thrift.transport.TServerSocket.acceptImpl(
        at org.apache.thrift.transport.TServerTransport.accept(
        at org.apache.thrift.server.TThreadPoolServer.serve(
        at org.apache.cassandra.thrift.CassandraDaemon.start(
        at org.apache.cassandra.thrift.CassandraDaemon.main(
Caused by: Too many open files
        at Method)
        at org.apache.thrift.transport.TServerSocket.acceptImpl(
        ... 5 more

The client was reporting timeouts in this case.

The max fd limit on the process was in fact not exceedingly high
(1024) and raising it seems to have solved the problem.

Anyway It still seems that there may be two issues:

- since we had never seen this error before with normal client
connections (as in: non hadoop), is it possible that the
Cassandra/hadoop layer is not closing sockets properly between one
connection and the other, or not reusing connections efficiently?
E.g. TSocket seems to have a close() method but I don't see it used in
ColumnFamilyInputFormat.(getSubSplits, getRangeMap) but it may well be
inside CassandraClient.

Anyway, judging by lsof's output I can only see about a hundred TCP
connections, but those from the hadoop jobs seem to always be below 60
so this may just be my wrong impression.

- is it possible that such errors show up on the client side as
timeoutErrors when they could be reported better? this would probably
help other people in diagnosing/reporting internal errors in the

Thanks again to everyone with this, I promise I'll put the discussion
on the wiki for future reference :)

View raw message