em, I'll be happy to provide more info.
Alexis Lauthier
De : aaron morton
À : user@cassandra.apache.org
Envoyé le : Mardi 17 Janvier 2012 1h49
Objet : Re: Compressed families not created on new node
eeek, HW errors.
I would guess (thats all it is)
" IOExceptions have been routinely logged for
> 13 days now.
>
> The best idea I can come up with now is: decommission the failing node, then
> add the new node. And hope the schema will fully replicate. This will leave
> me with only one node for a time, and I'm not sur
r ideas ?
Thanks,
Alexis Lauthier
De : aaron morton
À : user@cassandra.apache.org
Envoyé le : Lundi 16 Janvier 2012 1h05
Objet : Re: Compressed families not created on new node
Without knowing what the IOErrors are I would do the following:
nodetool scrub
few days ago.
> All "nodetool repair" calls have been blocking since then.
>
> Any ideas on how I can get the data on the new node, before the old one dies?
>
>
> Thanks,
> Alexis Lauthier
>
>
> De : aaron morton
> À : user@cassandra.apache.org
> E
nks,
Alexis Lauthier
De : aaron morton
À : user@cassandra.apache.org
Envoyé le : Dimanche 15 Janvier 2012 19h17
Objet : Re: Compressed families not created on new node
Sounds like the schema has not fully migrated to the new node. It is applied to
the joining node one
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
I'm using Cassandra 1.0.3 on a 2 nodes cluster. My schema (with
replication_factor=2) contains both compressed (with
sstable_compression=DeflateCompressor) and uncompressed column families.
When bootstrapping a third node, the uncompressed families are created on the
new node as expected, but
