Thanks Jeff.
Rajath Subramanyam
On Thu, Mar 23, 2017 at 4:50 PM, Jeff Jirsa wrote:
> The ancestors were used primarily to clean up leftovers in the case that
> cassandra was killed right as compaction finished, where the
> source/origin/ancestors
The ancestors were used primarily to clean up leftovers in the case that
cassandra was killed right as compaction finished, where the
source/origin/ancestors were still on the disk at the same time as the
compaction result.
It's not timestamp based, though - that compaction process has moved to
Thanks, Jeff. Did all the internal tasks and the compaction tasks move to a
timestamp-based approach?
Regards,
Rajath
Rajath Subramanyam
On Thu, Mar 23, 2017 at 2:12 PM, Jeff Jirsa wrote:
> That information was removed, because it was really meant
That information was removed, because it was really meant to be used for a
handful of internal tasks, most of which were no longer used. The remaining
use was cleaning up compaction leftovers, and the compaction leftover code
was rewritten in 3.0 / CASSANDRA-7066 (note, though, that it's somewhat
Hello Cassandra-Users and Cassandra-dev,
One of the handy features in sstablemetadata that was part of Cassandra
2.1.15 was that it displayed Ancestor information of an SSTable. Here is a
sample output of the sstablemetadata tool with the ancestors information in
C* 2.1.15:
[centos@chen-datos