That sounds like to many sstables.
Out of interest were you using multi threaded compaction ? Just wondering about
this
https://issues.apache.org/jira/browse/CASSANDRA-3711
Can you set the file handles to unlimited ?
Can you provide some more info what your see in the data dir incase it is a
Without knowing what the IOErrors are I would do the following:
nodetool scrub to fix any on disk errors, this will also take a snapshot you
can use for rollback.
nodetool repair to ensure data is consistent.
Hope that helps.
-
Aaron Morton
Freelance Developer
@aaronmorton
Sounds like you need a custom, manual solution.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 12/01/2012, at 9:09 AM, David McNelis wrote:
> Right.
>
> One of the challenges though is if the key's wouldn't necessarily directly
> transl
Sorry, my english is not very well on sundays. By "partage" i mean "to
share" and by greate I mean "great".
Anyway, thanks everybody for your answers.
Carlos Pérez Miguel
El día 15 de enero de 2012 21:53, Carlos Pérez Miguel
escribió:
> If you can partage it would be greate
>
> Carlos Pérez M
If you can partage it would be greate
Carlos Pérez Miguel
2012/1/15 Віталій Тимчишин :
> Yep. Have written groovy script this friday to perform autobalancing :) I am
> going to add it to my jenkins soon.
>
>
> 2012/1/15 Maxim Potekhin
>>
>> I see. Sure, that's a bit more complicated and you'd
Yep. Have written groovy script this friday to perform autobalancing :) I
am going to add it to my jenkins soon.
2012/1/15 Maxim Potekhin
> I see. Sure, that's a bit more complicated and you'd have to move tokens
> after adding a machine.
>
> Maxim
>
>
>
> On 1/15/2012 4:40 AM, Віталій Тимчишин
I see. Sure, that's a bit more complicated and you'd have to move tokens
after adding a machine.
Maxim
On 1/15/2012 4:40 AM, ??? wrote:
It's nothing wrong for 3 nodes. It's a problem for cluster of 20+
nodes, growing.
2012/1/14 Maxim Potekhin mailto:potek...@bnl.gov>>
I'm
I see only one line "JOINING: sleeping 3 ms for pending range setup".
Before that, I have a lot of migration INFO messages, only for the uncompressed
families.
I have currently killed the new node, so a describe cluster shows only one
schema version on the first two nodes.
[default@unknow
Sounds like the schema has not fully migrated to the new node. It is applied to
the joining node one change at a time. A quick scan of the changes file does
not find anything fixed after 1.0.3
You can check schema versions in the CLI using the describe cluster command.
Check for errors in the
If you are doing a straight one-to-one copy from one cluster to another try…
1) nodetool snapshot on each prod node for the system and application key
spaces.
2) rsync system and app key space snapshots
3) update the yaml files on the new cluster to have the correct initial_tokens.
This is not n
If you can handle the load without the three machines, and you are still
meeting your redundancy requirements removing them may make your life easier.
Otherwise you have to consider that your cluster is made up of machines with
the worst parts from all of the nodes (i.e. lowest memory, slowest c
may be it's what you are looking for :
http://planetcassandra.org/posts?page=15
?
2012/1/13 Sunit Randhawa
> Hello,
>
> Wondering how would one add Composite Keys rows using CLI. Supposing we
> have CF defined below:
>
> create column family ListTransactions
> with comparator =
> 'CompositeTyp
It's nothing wrong for 3 nodes. It's a problem for cluster of 20+ nodes,
growing.
2012/1/14 Maxim Potekhin
> I'm just wondering -- what's wrong with manual specification of tokens?
> I'm so glad I did it and have not had problems with balancing and all.
>
> Before I was indeed stuck with 25/25/
13 matches
Mail list logo
