[ https://issues.apache.org/jira/browse/CASSANDRA-14939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Blake Eggleston updated CASSANDRA-14939: ---------------------------------------- Reviewer: Marcus Eriksson Fix Version/s: 4.0 Status: Patch Available (was: Open) |[trunk|https://github.com/bdeggleston/cassandra/tree/14939-trunk]|[dtests|https://github.com/bdeggleston/cassandra-dtest/tree/14939]|[circle|https://circleci.com/workflow-run/587857d3-8d7a-4710-906f-010f499d4910]| This adds {{\-\-cleanup}}, {{\-\-summarize-pending}}, and {{\-\-summarize-repaired}} flags to {{nodetool repair_admin}}. Each of which also accept keyspace/table and range args. To support reporting the min/max repairedAt time for a given token range across restarts, I had to alter the logic for purging old sessions. Finalized sessions will only be deleted if there is a newer session covering it's ranges. > fix some operational holes in incremental repair > ------------------------------------------------ > > Key: CASSANDRA-14939 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14939 > Project: Cassandra > Issue Type: Bug > Reporter: Blake Eggleston > Assignee: Blake Eggleston > Priority: Major > Fix For: 4.0 > > > Incremental repair has a few operational rough spots that make it more > difficult to fully automate and operate at scale than it should be. > * Visibility into whether pending repair data exists for a given token range. > * Ability to force promotion/demotion of data for completed sessions instead > of waiting for compaction. > * Get the most recent repairedAt timestamp for a given token range. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org