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 deleted automagically. And - what is the suggested way to solve that problem? Should i try again tar-ing the snapshot until it doesn't happen anymore that something changes in between? Or is there a way to "pause" the incremental repairs? > 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 cassandra cluster. >> >> Cassandra version: >> 2.1.11 >> >> What i basically do: >> 1. nodetool snapshot >> 2. tar all snapshot folders into one file >> 3. transfer them to another server >> >> What happens is that tar just sometimes give the error message "file changed >> as we read it" while its adding a .db-file from the folder of the previously >> created snapshot. >> If i understand everything correct, this SHOULD never happen. Snapshots >> should be totally immutable, right? >> >> Am i maybe hitting a bug or is there some rare case with running repair >> operations or what-so-ever which can change snapshotted data? >> I already searched through cassandra jira but couldn't find a bug which >> looks related to this behaviour. >> >> Would love to get some help on this. >> >> — >> Paul Dunkler > — Paul Dunkler ** * * UPLEX - Nils Goroll Systemoptimierung Scheffelstraße 32 22301 Hamburg tel +49 40 288 057 31 mob +49 151 252 228 42 fax +49 40 429 497 53 xmpp://pauldunk...@jabber.ccc <xmpp://pauldunk...@jabber.ccc>.de http://uplex.de/ <http://uplex.de/>
signature.asc
Description: Message signed with OpenPGP using GPGMail
