This sort of explain this, yes, but what solution can I use?
I do see the OPP writes go faster than the RP, so this makes sense that when
using the OPP there's higher chance that a host will fall behind with
compaction and eventually crash. It's not a nice feature, but hopefully
there are
On Sun, Feb 21, 2010 at 10:01 AM, Ran Tavory ran...@gmail.com wrote:
I'm also no clear whether CASSANDRA-804 is going to be a real fix.
There's one way to find out. :P
Ran,
There are bounds to how large your data directory will grow, relative to the
actual data. Please read up on compaction:
http://wiki.apache.org/cassandra/MemtableSSTable , and if you have a
significant number of deletes occuring, also read
On Sat, Feb 20, 2010 at 12:20 PM, Jonathan Ellis jbel...@gmail.com wrote:
We don't use native java serialization for anything but the on-disk
BitSets in our bloom filters (because those are deserialized once at
startup, so the overhead doesn't matter), btw.
Right, tangential use is pretty
On Wed, Feb 3, 2010 at 7:45 PM, Brian Frank Cooper
coop...@yahoo-inc.com wrote:
One thing that is puzzling is the scan performance. The scan experiment is to
scan between 1-100 records on each request. My 6 node Cassandra cluster is
only getting up to about 230 operations/sec, compared to
Dear all,
I want to change partitioner from Random to OrderPreserving. How can I do
with old data?
Thank a lot for support.
--
Best regards,
JKnight
[replying to list, with permission]
On Mon, Feb 22, 2010 at 12:05 AM, jeremey.barr...@nokia.com wrote:
I'm looking for a very scalable primary data store for a large web/API
application. Our data consists largely of lists of things, per user. So a
user has a bunch (dozens to hundreds) of
