[
https://issues.apache.org/jira/browse/CASSANDRA-20614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-20614:
------------------------------------------
Status: Ready to Commit (was: Review In Progress)
> Ensure DiskErrorsHandler initialization failures kill startup rather than
> allow a no-op handler
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20614
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20614
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Caleb Rackliffe
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If {{DiskErrorsHandlerService.set()}} is unable to assign a
> {{DiskErrorsHandler}}, we should probably kill startup rather than just
> issuing a WARNing in the logs. It's one thing to log a warning if the closure
> of an old handler goes wrong, but in the normal case, where we use the
> default handler, there could be potentially disastrous consequences of just
> starting without it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
