unable to rename commitlog, cassandra can't accept writes

2012-07-07 Thread Frank Hsueh
Hi,

I'm running Casandra 1.1.2 on Java 7 x64 on Win7 sp1 x64 (all latest
versions).  If it matters, I'm using a late version of Astyanax as my
client.

I'm using 4 threads to write a lot of data into a single CF.

After several minutes of load (~ 30m at last incident), Cassandra stops
accepting writes (client reports an OperationTimeoutException).  I looked
at the logs and I see on the Cassandra server:


ERROR 18:00:42,807 Exception in thread Thread[COMMIT-LOG-ALLOCATOR,5,main]
java.io.IOError: java.io.IOException: Rename from
\var\lib\cassandra\commitlog\CommitLog-701533048437587.log to
703272597990002 failed
at
org.apache.cassandra.db.commitlog.CommitLogSegment.init(CommitLogSegment.java:127)
at
org.apache.cassandra.db.commitlog.CommitLogSegment.recycle(CommitLogSegment.java:204)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator$2.run(CommitLogAllocator.java:166)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(CommitLogAllocator.java:95)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.io.IOException: Rename from
\var\lib\cassandra\commitlog\CommitLog-701533048437587.log to
703272597990002 failed
at
org.apache.cassandra.db.commitlog.CommitLogSegment.init(CommitLogSegment.java:105)
... 5 more


Anybody else seen this before ?


-- 
Frank Hsueh | frank.hs...@gmail.com


Re: unable to rename commitlog, cassandra can't accept writes

2012-07-07 Thread Frank Hsueh
bug already reported:

https://issues.apache.org/jira/browse/CASSANDRA-4337



On Sat, Jul 7, 2012 at 6:26 PM, Frank Hsueh frank.hs...@gmail.com wrote:

 Hi,

 I'm running Casandra 1.1.2 on Java 7 x64 on Win7 sp1 x64 (all latest
 versions).  If it matters, I'm using a late version of Astyanax as my
 client.

 I'm using 4 threads to write a lot of data into a single CF.

 After several minutes of load (~ 30m at last incident), Cassandra stops
 accepting writes (client reports an OperationTimeoutException).  I looked
 at the logs and I see on the Cassandra server:

 
 ERROR 18:00:42,807 Exception in thread Thread[COMMIT-LOG-ALLOCATOR,5,main]
 java.io.IOError: java.io.IOException: Rename from
 \var\lib\cassandra\commitlog\CommitLog-701533048437587.log to
 703272597990002 failed
 at
 org.apache.cassandra.db.commitlog.CommitLogSegment.init(CommitLogSegment.java:127)
 at
 org.apache.cassandra.db.commitlog.CommitLogSegment.recycle(CommitLogSegment.java:204)
 at
 org.apache.cassandra.db.commitlog.CommitLogAllocator$2.run(CommitLogAllocator.java:166)
 at
 org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(CommitLogAllocator.java:95)
 at
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
 at java.lang.Thread.run(Thread.java:722)
 Caused by: java.io.IOException: Rename from
 \var\lib\cassandra\commitlog\CommitLog-701533048437587.log to
 703272597990002 failed
 at
 org.apache.cassandra.db.commitlog.CommitLogSegment.init(CommitLogSegment.java:105)
 ... 5 more
 

 Anybody else seen this before ?


 --
 Frank Hsueh | frank.hs...@gmail.com




-- 
Frank Hsueh | frank.hs...@gmail.com