Details
-
Improvement
-
Status: Resolved
-
Low
-
Resolution: Fixed
-
None
-
Operability
-
Low Hanging Fruit
-
All
-
None
-
Description
When a node is joining a cluster, there is this output upon startup:
cassandra_node_6 | INFO [GossipStage:1] 2022-12-06 12:48:07,187 Gossiper.java:1413 - Node /172.19.0.5:7000 is now part of the cluster cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down. cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down. cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down. cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down. cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down. cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down. cassandra_node_6 | WARN MigrationCoordinator.java:650 - Can't send schema pull request: node /172.19.0.5:7000 is down.
This is there for a lot of already existing nodes. You got the idea. This log is misleading, it indeed can not pull requests because "node is down" but it is not down, it just thinks it is because Gossiper has not had a chance to receive any gossip about these nodes yet.
I put there more logs and it writes this:
MigrationCoordinator.java:655 - Can't send schema pull request: node /172.19.0.5:7000 is down: NORMAL, isAlive: false
When I do this:
if (!gossiper.hasEndpointState(endpoint)) return; if (!gossiper.isAlive(endpoint)) { EndpointState endpointStateForEndpoint = gossiper.getEndpointStateForEndpoint(endpoint); String status = Gossiper.getGossipStatus(endpointStateForEndpoint); logger.warn("Can't send schema pull request: node {} is down: {}, isAlive: {}", endpoint, status, endpointStateForEndpoint.isAlive()); callback.onFailure(endpoint, RequestFailureReason.UNKNOWN); return; }
So it is in NORMAL but it is not alive yet which is quite strange.
The fix is to still return prematurely but we would not skip the logging on WARN only in case isAlive is false and status is _not_NORMAL. We would however still log on TRACE at least.