Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ycsb cassandra fails on GCE #429

Closed
vladzcloudius opened this issue Jul 31, 2014 · 2 comments
Closed

ycsb cassandra fails on GCE #429

vladzcloudius opened this issue Jul 31, 2014 · 2 comments
Labels
Milestone

Comments

@vladzcloudius
Copy link

How to reproduce the issue ?

Run cassandra on osv vm with 4 cpu and 3.8 G memory.
Run ycsb from Linux vm (https://github.com/cloudius-systems/osv/wiki/Benchmarking-Cassandra-and-other-NoSQL-databases-with-YCSB).
I usually ran workloadf with -threads 100 -p operationcount=1000000 -p recordcount=800000 so my load command line looks like that:
./bin/ycsb load cassandra-10 -threads 100 -p operationcount=1000000 -p recordcount=800000 -p hosts=osv-vm-ip -P workloads/workloadf -s

Then one will see that ops per second become 0 and shortly the client will fail with a "broken pipe" error.

@dorlaor
Copy link
Contributor

dorlaor commented Jul 31, 2014

How does it fails?
Could it be there is not enough memory? Try w/ larger guest

On Thu, Jul 31, 2014 at 5:40 PM, vladzcloudius notifications@github.com
wrote:

  1. How to reproduce the issue ?
    Run cassandra on osv vm with 4 cpu and 3.8 G memory.
    Run ycsb from Linux vm (
    https://github.com/cloudius-systems/osv/wiki/Benchmarking-Cassandra-and-other-NoSQL-databases-with-YCSB
    ).
    I usually ran workloadf with -threads 100 -p operationcount=1000000 -p
    recordcount=800000 so my load command line
    looks like that:
    ./bin/ycsb load cassandra-10 -threads 100 -p operationcount=1000000 -p
    recordcount=800000 -p hosts=osv-vm-ip -P workloads/workloadf -s

After a while one will see the


Reply to this email directly or view it on GitHub
#429.

@slivne slivne added the bug label Aug 3, 2014
@slivne slivne added this to the release 0.12 milestone Aug 3, 2014
@vladzcloudius
Copy link
Author

It's been noticed that this test blows off the Guest storage quite quickly (in about 1100-1800 seconds of the test) and eventually causes the following cassandra assert:

ERROR 12:06:11,457 Exception in thread Thread[CompactionExecutor:18,1,main]
FSWriteError in /var/lib/cassandra/data/usertable/data/usertable-data-tmp-jb-218-Filter.db
at org.apache.cassandra.io.sstable.SSTableWriter$IndexWriter.close(SSTableWriter.java:478)
at org.apache.cassandra.io.util.FileUtils.closeQuietly(FileUtils.java:212)
at org.apache.cassandra.io.sstable.SSTableWriter.abort(SSTableWriter.java:304)
at org.apache.cassandra.db.compaction.CompactionTask.runWith(CompactionTask.java:209)
at org.apache.cassandra.io.util.DiskAwareRunnable.runMayThrow(DiskAwareRunnable.java:48)
at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:60)
at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:59)
at org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionTask.run(CompactionManager.java:198)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
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:744)
Caused by: java.io.FileNotFoundException: /var/lib/cassandra/data/usertable/data/usertable-data-tmp-jb-218-Filter.db (No space left on device)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:221)
at java.io.FileOutputStream.(FileOutputStream.java:110)
at org.apache.cassandra.io.sstable.SSTableWriter$IndexWriter.close(SSTableWriter.java:469)
... 13 more

So, this issue is a false alarm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants