Sounds like the keyspace was created on the 32GB machine, so it guessed memtable sizes that are too large when run on the 16GB one. Use "update column family" from the cli to cut the throughput and operations thresholds in half, or to 1/4 to be cautious.
On Mon, Feb 7, 2011 at 9:00 AM, Patrik Modesto <patrik.mode...@gmail.com> wrote: > On Mon, Feb 7, 2011 at 15:44, sridhar basam <s...@basam.org> wrote: >> Looks like you don't have a big enough working set from your GC logs, there >> doesn't seem to be a lot being reclaimed in the GC process. The process is >> reclaiming a few hundred MB and is running every few seconds. How big are >> your caches? The probable reason that it works the first couple times when >> you create it due to nothing being in cache as it gets built up. > > Hi Sridhar, > > thanks for your answer. I didn't set the cache to any specific value, > I use the defaults: > > [default@Foo] show keyspaces; > Keyspace: Foo: > Replication Strategy: org.apache.cassandra.locator.SimpleStrategy > Replication Factor: 1 > Column Families: > ColumnFamily: Url > Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type > Row cache size / save period: 0.0/0 > Key cache size / save period: 200000.0/3600 > Memtable thresholds: 4.6640625/995/60 > GC grace seconds: 864000 > Compaction min/max thresholds: 4/32 > Read repair chance: 1.0 > Built indexes: [] > > My row-key is 16bytes long string, so I don't expect the cache would > be a problem. > > Patrik > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
