ah... my bad, thanks for the explanation! On Tue, Aug 14, 2012 at 1:57 PM, aaron morton <aa...@thelastpickle.com>wrote:
> The Priam code is looking for the <keyspace>/<columnfamily>/backups > directory created by cassandra during incremental backups. If it finds it > the files are uploaded to S3. > > It's taking the built in incremental backups off node. (AFAIK) > > Cheers > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 15/08/2012, at 8:16 AM, Yang <teddyyyy...@gmail.com> wrote: > > in the initial incremental backup implementation, > the hardlinking to the backup dir was in the CFS.addSSTable() code, so > it's part of the Cassandra code. > > I looked at Priam, > https://github.com/Netflix/Priam/blob/master/priam/src/main/java/com/netflix/priam/backup/IncrementalBackup.java > > this code pretty much does the same thing as the original addSSTable() > incremental backup . > so the Priam backup code operates outside of Cassandra write path? > any insight into why this approach was chosen instead of using the > incremental backup provided by Cassandra? > > thanks > Yang > > >