Don't call on(Up|Down|Add|Remove) methods if Cluster is closed/closing.

Description

I noticed the following exception rarely being raised when closing a Cluster instance at times:

I think this is a small side effect of calling signalConnectionFailure being moved from Connection#defunct to Connection#closeAsync in . We should check in the triggerOn* methods like we do in the on* methods to see if the cluster is closed/closing before submitting to the executor. In theory there still might be a very thin window where the executor is shutdown between a condition check and submitting the Task.

Environment

None

Pull Requests

None

Activity

Show:
Alexandre Dutra
June 21, 2020, 5:51 PM

This ticket has been closed on 2020-06-22 due to prolonged inactivity, as part of an automatic housekeeping procedure.

If you think that this was inappropriate, feel free to re-open the ticket. If possible, please provide any context that could explain why the issue described in this ticket is still relevant.

Also, please note that enhancements and feature requests cannot be accepted anymore for legacy driver versions (OSS 1.x, 2.x, 3.x and DSE 1.x).

Thank you for your understanding.

Won't Do

Assignee

Unassigned

Reporter

Andy Tolbert

Labels

None

PM Priority

None

Reproduced in

2.0.12

Affects versions

Fix versions

None

Pull Request

None

Doc Impact

None

Size

None

External issue ID

None

External issue ID

None

Priority

Minor
Configure