On 18.07.2013 19:19, Robert Coli wrote:
Why not just determine which SSTable is corrupt, remove it from the
restore set, then run a repair when you're done to be totally sure all
data is on all nodes?
This is what I did finally - was some kind of work, since sstableloader
just stopped with
On Thu, Jul 18, 2013 at 10:17 AM, Jan Kesten wrote:
> I think it might be corrupted due to a poweroutage. Apart from this issue
> reading the data with consistency level quorum (I have three replicas) did
> not issue an error - only the import to a different cluster.
>
> So, if I import all nodes
Hi,
I think it might be corrupted due to a poweroutage. Apart from this issue
reading the data with consistency level quorum (I have three replicas) did not
issue an error - only the import to a different cluster.
So, if I import all nodes except the one with the corrupted sstable - shoudn't
I
sstable might be corrupted due to bad disk. In that case, replication does
not matter.
On Thu, Jul 18, 2013 at 8:52 AM, Jan Kesten wrote:
> Hello together,
>
> today I experienced a problem while loading a snapshot from our cassandra
> cluster to test cluster. The cluster has six nodes and I to
Hello together,
today I experienced a problem while loading a snapshot from our
cassandra cluster to test cluster. The cluster has six nodes and I took
a snapshot from all nodes concurrently and tried to import them in the
other cluster.
From 5 out of 6 nodes importing went well with no erro
