Thanks Aaron for the response. I see those logs.
I had one more question. Looks like sstableloader takes only one directory
at a time. Is it possible to load multiple directories in one call.
Something like sstableloader /drive1/keyspace1 /drive2/keyspace1...
This way one can take adv of the speedu
if your keys are 1-n and you are using BOP, then almost certainly your
ring will be massively unbalanced with the first node getting clobbered.
You'll have bigger issues than getting lexical ordering.
I'd try to rethink your design so that you don't need BOP.
On 03/16/2012 06:49 PM, Watanabe M
How about to fill zeros before smaller digits?
Ex. 0001, 0002, etc
maki
On 2012/03/17, at 6:29, A J wrote:
> If I define my rowkeys to be Integer
> (key_validation_class=IntegerType) , how can I order the rows
> numerically ?
> ByteOrderedPartitioner orders lexically and retrieval usin
The Cassandra team has been released new version every month last half year.
So I anticipate they will release 1.0.9 before April. Just my forecast:-)
maki
On 2012/03/16, at 22:41, Johan Elmerfjord wrote:
> Perfect.. this helped a lot - and I can confirm that I have run in to the
> same issue
Hi guys,
While creating schema on our cluster today I didn't get any errors even
when some of the hosts in the cluster were unreachable (not the ones in the
same data centre but in another region). cli kept on showing all nodes
agreeing where all nodes were agreeing.
Now after this when I did "de
Doing reads and writes at CL=1 with RF=2 N=2 does not imply that the reads
will be inconsistent. It's more complicated than the simple counting of
blocked replicas. It is easy to support the notion that it will be largely
consistent, in fact very consistent for most use cases.
By default Cassandra
I would guess more aggressive compaction settings, did you update rows or
insert some twice?
If you run major compaction a couple times on the 0.8.1 cluster does the data
size get smaller?
You can use the "describe" command to check if compression got turned on.
-Jeremiah
_
If I define my rowkeys to be Integer
(key_validation_class=IntegerType) , how can I order the rows
numerically ?
ByteOrderedPartitioner orders lexically and retrieval using get_range
does not seem to make sense in order.
If I were to change rowkey to be UTF8 (key_validation_class=UTF8Type),
BOP st
I took the reset the world approach, things are much better now and the hints
table is staying empty. Bit disconcerting that it could get so large and not
be able to recover itself, but at least there was a solution. Thanks
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Thursday, M
Perfect.. this helped a lot - and I can confirm that I have run in to
the same issue as described in:
http://mail-archives.apache.org/mod_mbox/cassandra-user/201203.mbox/%
3CCALqbeQbQ=d-hORVhA-LHOo_a5j46fQrsZMm+OQgfkgR=4rr...@mail.gmail.com%3E
Where it goes down when it tries to move up files to a
You'll need to either read or write at at least quorum to get consistent
data from the cluster so you may as well do both.
Now that you mention it, I was wrong about downtime, with a two node
cluster reads or writes at quorum will mean both nodes need to be online.
Perhaps you could have an emergen
Sorry for such a late reply. I'm not always keeping up with the mailing
list.
> Is the following scenario covered by 2388? I have a test cluster of 6
> nodes with a replication factor of 3. Each server can execute hadoop
> tasks. 1 cassandra node is down for the test.
>
> The job is kicked off fr
Hi,
Since this thread already contains the system setup, I just want to ask
another question:
If you have 3 data centers (DC1,DC2 and DC3) and you have a keyspace where
the strategy options are such that each DC gets one replica. If you only
write to the nodes in one DC1 what is the path the repl
ok, thank you for your time!
Cheers
On 03/16/2012 10:12 AM, aaron morton wrote:
I think your original plan is sound.
1. Up the RF to 4.
2. Add the node with auto_bootstrap true
3. Once bootrapping has finished the new node has all the data it needs.
4. Check for secondary index creation using
I think your original plan is sound.
1. Up the RF to 4.
2. Add the node with auto_bootstrap true
3. Once bootrapping has finished the new node has all the data it needs.
4. Check for secondary index creation using describe in the CLI to see which
are build. You can also see progress using node
ahh, I think you may have hit a corner case here.
If the RF still 1 ?
> INFO [AntiEntropySessions:1] 2012-03-16 06:15:13,727
> AntiEntropyService.java (line 663) [repair #%s] No neighbors to repair
> with on range %s: session completed
Means there are no nodes which share the range with this no
ok, thank you both for the clarification. So the correct approach would
be to bootstrap the new node and run repair on each of the nodes in the
cluster.
I'm a bit puzzled though, I just tried to increase R to 3 in a cluster
with N=2. It serves reads and writes without issues CL.one. Is the
de
17 matches
Mail list logo
