[
https://issues.apache.org/jira/browse/CASSANDRA-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17572614#comment-17572614
]
Ekaterina Dimitrova edited comment on CASSANDRA-17782 at 7/28/22 7:06 PM:
--------------------------------------------------------------------------
[~benedict] , [~samt], [~maedhroz] maybe anyone of you wants to comment on this
as I see the DatabaseDescriptor.newFailureDetector was added in
CASSANDRA-16930?
was (Author: e.dimitrova):
[~benedict] , [~samt], [~maedhroz] maybe anyone of you want to comment on this
as I see the DatabaseDescriptor.newFailureDetector was added in
CASSANDRA-16930?
> `DatabaseDescriptor#clientInitialization` should set the `newFailureDetector`
> (maybe to a NoOpFailureDetector?)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17782
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17782
> Project: Cassandra
> Issue Type: Bug
> Reporter: Doug Rohrer
> Priority: Normal
>
> With the introduction of a configurable FailureDetector, client users of the
> {{cassandra-all}} jar now need to call not just `clientInitialization` but
> also `setDefaultFailureDetector` in order to avoid an NPE when the failure
> detector is constructed. This is a breaking change from previous versions
> where this was not necessary.
> Calls to {{DatabaseDescriptor#clientInitialization}} should set
> {{newFailureDetector}} to +something+, either by calling
> {{setDefaultFailureDetector}} or creating a different (NoOp?) FailureDetector.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
