Hi all,
We're running into a weird problem trying to migrate our data from a
1.2.10 cluster to a 2.0.3 one.
I've taken a snapshot on the old cluster, and for each host there, I'm running
sstableloader -d <host of new cluster> KEYSPACE/COLUMNFAMILY
(the sstableloader process from the 2.0.3 distribution, the one from
1.2.10 only gets java.lang.RuntimeException: java.io.IOException:
Connection reset by peer)
it then copies the data successfully but when checking the data i
noticed some rows seem to be missing. It turned out the data is not
missing, but has been tombstoned.
When I use sstable2json on the sstable on the destination cluster, it has
"metadata": {"deletionInfo":
{"markedForDeleteAt":1796952039620607,"localDeletionTime":0}}, whereas
it doesn't have that in the source sstable.
(Yes, this is a timestamp far into the future. All our hosts are
properly synced through ntp).
This has happened for a bunch of random rows. How is this possible?
Naturally, copying the data again doesn't work to fix it, as the
tombstone is far in the future. Apart from not having this happen at
all, how can it be fixed?
Best regards,
Mathijs
