You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/07/28 19:07:00 UTC

[jira] [Updated] (CASSANDRA-17782) `DatabaseDescriptor#clientInitialization` should set the `newFailureDetector` (maybe to a NoOpFailureDetector?)

     [ https://issues.apache.org/jira/browse/CASSANDRA-17782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekaterina Dimitrova updated CASSANDRA-17782:
--------------------------------------------
    Fix Version/s: 4.1.x

> `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
>             Fix For: 4.1.x
>
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org