[
https://issues.apache.org/jira/browse/CASSANDRA-19758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870684#comment-17870684
]
Benedict Elliott Smith commented on CASSANDRA-19758:
----------------------------------------------------
AccordIncrementalRepair test failures appear to predate this patch -
{{txnRepairTest}} is failing today, but it fails due to
{{WriteTimeoutException}}. It now completes the transaction successfully, but
there is a follow-up problem that leaves the cluster in a bad state for the
other tests. If they are run in isolation they succeed.
(Still investigating other failures and test history)
> Accord: CommandsForKey should self-prune
> ----------------------------------------
>
> Key: CASSANDRA-19758
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19758
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: Benedict Elliott Smith
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> CommandsForKey should periodically self-prune, so as to continue functioning
> well in-between garbage collections. This is a bit complicated, as once we
> prune we are left with potentially incomplete information, and have to
> sometimes load per-command information from disk. But the payoff is ensuring
> CommandsForKey objects - which drive the majority of the state machine - are
> kept to a reasonable size.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
