[
https://issues.apache.org/jira/browse/CASSANDRA-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17620:
--------------------------------------
Status: Ready to Commit (was: Review In Progress)
> Incremental repair leaks SomeRepairFailedException after switch away from
> flatMap
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-17620
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17620
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1.x
>
>
> This is an extension of CASSANDRA-17549.
> Incremental repair used to do a flatMap where it returned a failed future of
> SomeRepairFailedException; this would not trigger our failure logging to log
> it due to the fact the executor didn’t know about it and RepairRunnable knew
> to ignore that error, a change was made to use map and throw the exception,
> and later that behavior was updated to trigger uncaughtException handling
> which leaks this exception.
> To roll back to previous behavior, we should switch back to flatMap to avoid
> this logging
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
