I have always relied upon the "Starting listening for CQL clients" message
as a solid indicator of service readiness.
John
On Wed, Jan 8, 2020 at 3:37 PM Voytek Jarnot
wrote:
> Needing to know when Cassandra is finished initializing and is up &
> running.
>
> Had some scripts which were
I use a script that calls nodetool info. If nodetool info returns an error
(instance isn’t up, on the way up, etc.) then I return that same error code
(and I know the node is NOT OK). If nodetool info succeeds, I then parse the
output for each protocol to be up. A node can be up, but have
Use the nodetool status command.
nodetool status
Datacenter: us-east-1
=
Status=Up/Down|/ State=Normal/Leaving/Joining/Moving-- AddressLoad
Tokens Owns (effective) Host ID Rack
UN 10.0.1.115 205.6 KiB 256 66.9%
Needing to know when Cassandra is finished initializing and is up & running.
Had some scripts which were looking through system.log for "No gossip
backlog; proceeding", but that turns out not to be 100% reliable.
Is looking for "Starting listening for CQL clients" considered definitive?
I.E.,
