You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jai Bheemsen Rao Dhanwada (Jira)" <ji...@apache.org> on 2020/04/20 20:35:00 UTC
[jira] [Commented] (CASSANDRA-15645) Can't send schema pull
request: node /A.B.C.D is down
[ https://issues.apache.org/jira/browse/CASSANDRA-15645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088063#comment-17088063 ]
Jai Bheemsen Rao Dhanwada commented on CASSANDRA-15645:
-------------------------------------------------------
I had similar issue and looks like this is introduced in 3.11
https://fossies.org/diffs/apache-cassandra/3.10-src_vs_3.11.0-src/src/java/org/apache/cassandra/service/MigrationTask.java-diff.html
Does this cause any issue to the schema or data?
I am using C* version 3.11.3.
> Can't send schema pull request: node /A.B.C.D is down
> -----------------------------------------------------
>
> Key: CASSANDRA-15645
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15645
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Pierre Belanger apache.org
> Priority: Normal
>
> On a new cluster with Cassandra 3.11.5, each time a node joins the cluster the schema pull request happens before at least 1 node is confirmed up. On the first node it's fine but node #2 and following are all complaining with below WARN.
>
> {noformat}
> INFO [MigrationStage:1] 2020-03-16 16:49:32,355 ColumnFamilyStore.java:426 - Initializing system_auth.roles
> WARN [MigrationStage:1] 2020-03-16 16:49:32,368 MigrationTask.java:67 - Can't send schema pull request: node /A.B.C.D is down.
> WARN [MigrationStage:1] 2020-03-16 16:49:32,369 MigrationTask.java:67 - Can't send schema pull request: node /A.B.C.D is down.
> INFO [main] 2020-03-16 16:49:32,371 Gossiper.java:1780 - Waiting for gossip to settle...
> INFO [GossipStage:1] 2020-03-16 16:49:32,493 Gossiper.java:1089 - InetAddress /A.B.C.D is now UP
> INFO [HANDSHAKE-/10.205.45.19] 2020-03-16 16:49:32,545 OutboundTcpConnection.java:561 - Handshaking version with /A.B.C.D
> {noformat}
>
> It's not urgent to fix but the WARN create noise for no reason. Before trying to pull the schema, shouldn't the process wait for gossip to have at least 1 node "up"?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org