[
https://issues.apache.org/jira/browse/CASSANDRA-15191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-15191:
------------------------------------------
Summary: stop_paranoid disk failure policy is ignored on
CorruptSSTableException after node is up (was: stop_paranoid disk failure
policy race condition on startup)
> stop_paranoid disk failure policy is ignored on CorruptSSTableException after
> node is up
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15191
> Project: Cassandra
> Issue Type: Bug
> Reporter: Vincent White
> Priority: Normal
> Attachments: log.txt
>
>
> If the {{stop_paranoid}} disk failure policy is triggered during startup (for
> example by a compaction) before the node reaches CassandraDaemon.start(),
> CassandraDaemon.start() will start the client transport services and start
> listening for client connections regardless of the previous corrupt sstable
> exception.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
