Hmm, is issue caused by some 1.x version? Before it never occurred to us.
Op 11 aug. 2012 22:36 schreef Tyler Hobbs ty...@datastax.com het
volgende:
We've seen something similar when running on a 32bit JVM, so make sure
you're using the latest 64bit Java 6 JVM.
On Sat, Aug 11, 2012 at 11:59
Going through this page and it looks like indexes are stored locally
http://www.datastax.com/dev/blog/cassandra-with-solr-integration-details .
My question is what happens if one of the solr nodes crashes? Is the data
indexed again on those nodes?
Also, if RF 1 then is the same data being
Hello,
I'm looking a bit into Cassandra to see whether it would be something to
go with for my company. I searched through the Internet, looked through
the FAQs, etc. but there are still some few open questions. Hope I don't
bother anybody with the usual beginner questions ...
Is there a
When data is first written it does remain in memory until that memory is
flushed. After the data is only on disk, it remains there until a read
for that row-key/column is requested so in essense it's always load on
demand.
Currently there is no support for async notifications of changes.
On Sun, 12 Aug 2012 13:36:42 +0200, Robin Verlangen wrote:
Hmm, is issue caused by some 1.x version? Before it never occurred to us.
This bug was introduced in 1.1.0 and has been fixed in 1.1.3, where the
closed/recycled segments are now closed unmapped properly. The default
sizes are also
hi,
I wonder if disconnect! method works properly in gem cassandrabecause the code
below does not cause exception.
-
client = Cassandra.new('pool', host_ip)
ret = client.get(:db, 'test', key, option_one)p retclient.disconnect!
ret = client.get(:db, 'test', key, option_one)p ret
Thanks Dave. Does anybody know of a distributed in-memory system that can do
this and that supports structured data (e.g. tables)?
/Oliver
Am 12.08.2012 um 21:39 schrieb Dave Brosius dbros...@mebigfatguy.com:
When data is first written it does remain in memory until that memory is
flushed.
Installed 1.1.3 on my Linux cluster - the JVM_OPTS were truncated due to
a script error in Cassandra-env.sh:
Invalid token in the following.
startswith () [ ${1#$2} != $1 ]
