Lazy initialization of Cluster

Description

Upon creation a Cluster instance immediately tries to connect to the configured hosts. If this attempt fails, the Cluster's constructor throws an exception and does not try to reconnect. This means that in deployments that constitute both Cassandra servers and clients, a strict order must be preserved (so that the server is up before the client is started) or the client bootstrap sequence fails. Another option is to have special code to handle reconnection attempts must be provided that wrap the Cluster's creation.

Environment

None
Done

Assignee

Jorge Bay Gondra

Reporter

Jorge Bay Gondra

Labels

None

PM Priority

None

Fix versions

External issue ID

None

Doc Impact

None

Reviewer

None

Pull Request

None

Epic Link

None

Sprint

None

Pull Requests

None

Size

S

Components

Priority

Major
Configure