Hi,
What is the recommended way to avoid range ghost in using get_range()?In my
case, order of the key is not problem. It seems valid to use random :start_key
in every query, but i'm new to cassandra and do not know if it'srecommended or
not.
I use Cassandra 1.1.4 and ruby client. Range ghosts h
hi,
One node in my cluster stay in "joining". I found a jira about this, which is
fixed,but still sees the similar thing. This is a node I remove the token first
becauseit did not boot correctly and re-joined in the cluster without any
pre-set token(shouldI set the previous token?).
As you see b
Tyler,
yeah, i found those.thanks for your help.
satoshi
--- On Tue, 2012/9/4, Tyler Hobbs wrote:
There are several logs associated with each minor compaction. Grep your logs
for "Compacting".
On Mon, Sep 3, 2012 at 7:41 AM, Satoshi Yamada
wrote:
hi,
i know minor compaction
hi,
i know minor compaction is caused when the num of SSTableexceeds the thresholds.
then, is there anyway to find what time minor compaction happened?is minor
compaction output into log?
thanks,satoshi
://github.com/twitter/cassandra/issues
Cheers
-Aaron MortonFreelance
Developer@aaronmortonhttp://www.thelastpickle.com
On 13/08/2012, at 2:27 PM, Satoshi Yamada wrote:
hi,
I wonder if disconnect! method works properly in gem cassandrabecause the code
below does not cause exception
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
---