Hi there,
just for your information: I found out whats actually happening.
It's not the file content which is changing. It's the number of hard links to
the files which is changing because during the tar is running, some incremental
backups are created.
In that case, tar gives a warning that
Hi Reynald,
> If I understand correctly, you are making a tar file with all the folders
> named "snapshots" (i.e. the folder under which all the snapshots are created.
> So you have one snapshots folder per table).
No, Thats not the case. We are doing a nightly snapshot of the whole database
Hi Paul,
If I understand correctly, you are making a tar file with all the
folders named "snapshots" (i.e. the folder under which all the snapshots
are created. So you have one /snapshots /folder per table).
If this is the case, when you are executing "nodetool repair", Cassandra
will create
> I guess this might come from the incremental repairs...
> The repair time is stored in the sstable (RepairedAt timestamp metadata).
By the way: We are not using incremental repairs at all. So can't be the case
here.
It really seems like there is somewhat that can still change data in snapshot
Hi Mike,
> Hi Paul, what is the value of the snapshot_before_compaction property in your
> cassandra.yaml?
snapshot_before_compaction: false
> Say if another snapshot is being taken (because compaction kicked in and
> snapshot_before_compaction property is set to TRUE) and at this moment
Hi Paul, what is the value of the snapshot_before_compaction property in
your cassandra.yaml?
Say if another snapshot is being taken (because compaction kicked in and
snapshot_before_compaction property is set to TRUE) and at this moment
you're tarring the snapshot folders..
Maybe can take a
And - as an addition:
Shoudln't that be documented that even snapshot files can change?
> I guess this might come from the incremental repairs...
>> The repair time is stored in the sstable (RepairedAt timestamp metadata).
>
> ok, that sounds interesting.
> Could that also happen to incremental
Hi there,
> I guess this might come from the incremental repairs...
> The repair time is stored in the sstable (RepairedAt timestamp metadata).
ok, that sounds interesting.
Could that also happen to incremental backup files as well? I had another case
where incremental backup files were totally
Hi Paul,
I guess this might come from the incremental repairs...
The repair time is stored in the sstable (RepairedAt timestamp metadata).
Cheers,
Reynald
On 31/05/2016 11:03, Paul Dunkler wrote:
Hi there,
i am sometimes running in very strange errors while backing up
snapshots from a
