[
https://issues.apache.org/jira/browse/CASSANDRA-17561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693679#comment-17693679
]
Paulo Motta commented on CASSANDRA-17561:
-----------------------------------------
{quote}Why do we want to know what ranges that snapshot covers? What is the use
case?
{quote}
This would be additional metadata to enrich the snapshot manifest, just to
indicate that particular snapshot covers a subset of ranges (and not all ranges
as standard snapshots). While this could be useful if this functionality was
available to external users, I don't think this is a big deal for
internal/ephemeral snapshots since they're removed anyway after repair
completes.
{quote}btw isnt it true that as soon as there is some topology change and nodes
are not responsible for so and so ranges anymore, that information in snapshot
is pretty much useless, no?
{quote}
The metadata could be useful to easily identify that a snapshot is no longer
"valid" when a node's changes ranges. I think this would be a nice to have but
shouldn't block this ticket. Perhaps we can reconsider if we decide to expose
the "partial" snapshot functionality to external users.
> Diagnostic snapshot service should only snapshot mismatching ranges on
> preview repair mismatch
> ----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17561
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17561
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> We currently snapshot all sstables in a table when a preview repair mismatch
> occurs, we should only snapshot the sstables containing the mismatching ranges
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
