[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943010#comment-13943010 ] Aleksander Stasiak commented on CASSANDRA-6799: --- I'm facing same problem: I've cluster created with 1.1.7, then migrated through 1.2.10 to 2.0.x.(currently x==6). After adding a new node in a new DC I get a new version of schema. Later on, after few restarts of the new node a schema will probably be agreed, but there is still a problem: I've authentication enabled, and after all I can't login to the system, cassandra sees, that my login is stored on the new node(RF=1), but there is no data on it, even repair does not copy data from the old nodes. So when i try to login, the system says, that the user does not exists. I don't know how to deal with it, maybe the cause of the problem is a fact, that new node tries to create KS system_auth (and system_traces, too), without migrating the schema? I don't have a deep knowledge, how it's implemented, it's just a guess. Maybe it is because of the fact, that the old nodes use token, but the new one uses vnodes? schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 |
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934802#comment-13934802 ] Duncan Sands commented on CASSANDRA-6799: - Something I noticed while working with 2.0.5 (I'm now on 2.0.6 but didn't make any schema changes yet) is that dropping a table resulted in schema version disagreements all over the cluster, i.e. before dropping the table all nodes agreed on the schema version, after dropping the table this was no longer the case. Restarting all nodes fixed this. On the other hand, adding tables didn't cause any trouble: all nodes immediately moved to the same new schema version. Maybe it was due to CASSANDRA-6700, in which case 2.0.6 should be OK. schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 (14 rows) I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[
https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13931690#comment-13931690
]
Pas commented on CASSANDRA-6799:
Hello!
We're experiencing something very similar, although with a substantially higher
schema traffic and after a few restart-restarts the schemas (on just a 2-node
ring, 2.0.6 both), finally agreed, but after running a few keyspace creates and
drops they drifted again.
{code}
root@test1:/var/log/cassandra# nodetool gossipinfo | grep SCH
SCHEMA:23bf64b8-bfae-3d4a-a238-220731bda1eb
SCHEMA:23bf64b8-bfae-3d4a-a238-220731bda1eb
root@test1:/var/log/cassandra#
root@test1:/var/log/cassandra# nodetool gossipinfo | grep SCH
SCHEMA:fe69b71a-90d7-3c99-a6a7-f5e6b10ed6d1
SCHEMA:fe69b71a-90d7-3c99-a6a7-f5e6b10ed6d1
root@test1:/var/log/cassandra# nodetool gossipinfo | grep SCH
SCHEMA:fe69b71a-90d7-3c99-a6a7-f5e6b10ed6d1
SCHEMA:fe69b71a-90d7-3c99-a6a7-f5e6b10ed6d1
root@test1:/var/log/cassandra# nodetool gossipinfo | grep SCH
SCHEMA:a8f444f9-7860-335c-96a1-1beeebca543f
SCHEMA:15abe898-418f-3fdf-b862-cf06b907704e
root@test1:/var/log/cassandra#
root@test1:/var/log/cassandra# nodetool gossipinfo | grep SCH
SCHEMA:a8f444f9-7860-335c-96a1-1beeebca543f
SCHEMA:15abe898-418f-3fdf-b862-cf06b907704e
{code}
{code}
## this is test2
[default@unknown] create keyspace test13;
fe69b71a-90d7-3c99-a6a7-f5e6b10ed6d1
[default@unknown] drop keyspace test11;
0a96652e-0524-3875-997b-cea2c20291bf
[default@unknown] drop keyspace test12;
c7f7ff34-a70b-3da5-88a8-70ceef91b2e9
[default@unknown] drop keyspace test14;
Keyspace 'test14' not found.
[default@unknown] drop keyspace test13;
a8f444f9-7860-335c-96a1-1beeebca543f
[default@unknown] drop keyspace test13;
Keyspace 'test13' not found.
{code}
schema_version of newly bootstrapped nodes disagrees with existing nodes
Key: CASSANDRA-6799
URL: https://issues.apache.org/jira/browse/CASSANDRA-6799
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5
Reporter: Duncan Sands
Attachments: system.log.gz
After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I
noticed that they have a different schema_version to the existing nodes. The
existing nodes have all been around for a while, saw some schema changes in
the past (eg: timeuuid - timestamp on a column family) but none recently,
and were originally running 1.2 (they were upgraded to 2.0.5). Here you see
the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two
nodes:
cqlsh select peer, data_center, host_id, preferred_ip, rack,
release_version, rpc_address, schema_version from system.peers;
peer | data_center | host_id |
preferred_ip | rack | release_version | rpc_address| schema_version
+-+--+--+--+-++--
192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 |
null | RAC1 | 2.0.5 | 192.168.21.12 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee |
null | RAC1 | 2.0.5 | 172.18.33.24 |
0d9173d5-3947-328e-a14d-ce05239f61e0
172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e |
null | RAC1 | 2.0.5 | 172.18.33.22 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 |
null | RAC1 | 2.0.5 | 192.168.60.136 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd |
null | RAC1 | 2.0.5 | 192.168.60.137 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 |
null | RAC1 | 2.0.5 | 192.168.21.11 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f |
null | RAC1 | 2.0.5 | 172.18.33.21 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 |
null | RAC1 | 2.0.5 | 192.168.60.138 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 |
null | RAC1 | 2.0.5 | 192.168.60.134 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d |
null | RAC1 | 2.0.5 | 172.18.33.23 |
0d9173d5-3947-328e-a14d-ce05239f61e0
192.168.60.130 |
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920631#comment-13920631 ] Duncan Sands commented on CASSANDRA-6799: - I restarted one of the new nodes last night (neither had been restarted since it was bootstrapped), and now all nodes have the same schema version: not just the restarted node, but also the other newly bootstrapped node. schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 (14 rows) I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920639#comment-13920639 ] Duncan Sands commented on CASSANDRA-6799: - To be more precise, all nodes are now at schema version f673ced0-8cfd-3d69-baba-4f81dc60c5b5 schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 (14 rows) I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919761#comment-13919761 ] Duncan Sands commented on CASSANDRA-6799: - Just to clarify: the cluster was first upgraded to 2.0.5, then later two entirely new 2.0.5 nodes were bootstrapped into it; it is these two nodes that have a different schema_version to the others. schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 (14 rows) I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[
https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919781#comment-13919781
]
Brandon Williams commented on CASSANDRA-6799:
-
Hmm, it does look like some schema changes came in after it thought it was done
receiving the schema, but even so that should ultimately resolve itself. Do
you see any actually differences in the schema, and could you attach the output
from {{nodetool gossipinfo}} from one of the nodes?
schema_version of newly bootstrapped nodes disagrees with existing nodes
Key: CASSANDRA-6799
URL: https://issues.apache.org/jira/browse/CASSANDRA-6799
Project: Cassandra
Issue Type: Bug
Components: Core
Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5
Reporter: Duncan Sands
Attachments: system.log.gz
After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I
noticed that they have a different schema_version to the existing nodes. The
existing nodes have all been around for a while, saw some schema changes in
the past (eg: timeuuid - timestamp on a column family) but none recently,
and were originally running 1.2 (they were upgraded to 2.0.5). Here you see
the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two
nodes:
cqlsh select peer, data_center, host_id, preferred_ip, rack,
release_version, rpc_address, schema_version from system.peers;
peer | data_center | host_id |
preferred_ip | rack | release_version | rpc_address| schema_version
+-+--+--+--+-++--
192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 |
null | RAC1 | 2.0.5 | 192.168.21.12 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee |
null | RAC1 | 2.0.5 | 172.18.33.24 |
0d9173d5-3947-328e-a14d-ce05239f61e0
172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e |
null | RAC1 | 2.0.5 | 172.18.33.22 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 |
null | RAC1 | 2.0.5 | 192.168.60.136 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd |
null | RAC1 | 2.0.5 | 192.168.60.137 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 |
null | RAC1 | 2.0.5 | 192.168.21.11 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f |
null | RAC1 | 2.0.5 | 172.18.33.21 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 |
null | RAC1 | 2.0.5 | 192.168.60.138 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 |
null | RAC1 | 2.0.5 | 192.168.60.134 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d |
null | RAC1 | 2.0.5 | 172.18.33.23 |
0d9173d5-3947-328e-a14d-ce05239f61e0
192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 |
null | RAC1 | 2.0.5 | 192.168.60.130 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 |
null | RAC1 | 2.0.5 | 192.168.60.133 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 |
null | RAC1 | 2.0.5 | 192.168.60.135 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 |
null | RAC1 | 2.0.5 | 192.168.60.131 |
f673ced0-8cfd-3d69-baba-4f81dc60c5b5
(14 rows)
I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919790#comment-13919790 ] Duncan Sands commented on CASSANDRA-6799: - On one of the new nodes (172.18.33.23): $ nodetool gossipinfo /172.18.33.22 INTERNAL_IP:172.18.33.22 HOST_ID:75c9c81f-b00b-4335-8483-fb7f1bc0be1e LOAD:1.5064854213E10 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:ldn SEVERITY:0.251889169216156 STATUS:NORMAL,-1064547807964040726 RPC_ADDRESS:172.18.33.22 /192.168.60.137 INTERNAL_IP:192.168.60.137 HOST_ID:b12e6d71-e189-4fe8-b00a-8ff2cc9848fd LOAD:9.098685209E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.0 STATUS:NORMAL,-1043390449076482985 RPC_ADDRESS:192.168.60.137 /192.168.60.134 INTERNAL_IP:192.168.60.134 HOST_ID:7b860a54-59ea-4a92-9b47-44b52793cc70 LOAD:7.699225119E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.755667507648468 STATUS:NORMAL,-1336289368408026811 RPC_ADDRESS:192.168.60.134 /172.18.33.24 INTERNAL_IP:172.18.33.24 HOST_ID:6e634206-94b6-4dcf-9cf8-72bfe190feee LOAD:9.019441781E9 RELEASE_VERSION:2.0.5 NET_VERSION:7 RACK:RAC1 SCHEMA:0d9173d5-3947-328e-a14d-ce05239f61e0 DC:ldn SEVERITY:0.0 STATUS:NORMAL,-1037222479577374666 RPC_ADDRESS:172.18.33.24 /192.168.60.131 INTERNAL_IP:192.168.60.131 HOST_ID:d8b7b0b2-d697-43ae-ad6e-982b24637865 LOAD:7.806456384E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.0 STATUS:NORMAL,-1103418420199371943 RPC_ADDRESS:192.168.60.131 /192.168.21.12 INTERNAL_IP:192.168.21.12 HOST_ID:55e4b4b6-2e64-4542-87a4-d8a8e28b5135 LOAD:1.5401832752E10 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:rdm SEVERITY:0.0 STATUS:NORMAL,-1042286267161494289 RPC_ADDRESS:192.168.21.12 /192.168.60.132 INTERNAL_IP:192.168.60.132 HOST_ID:3327fc74-6583-48c1-838b-aad42376b0c1 LOAD:8.352198576E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.0 STATUS:NORMAL,-1016310801246170431 RPC_ADDRESS:192.168.60.132 /192.168.60.136 INTERNAL_IP:192.168.60.136 HOST_ID:c83d403f-ef0d-4c54-a844-d69730fa54d3 LOAD:9.46574924E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.0 STATUS:NORMAL,-1092634661963868178 RPC_ADDRESS:192.168.60.136 /172.18.33.21 INTERNAL_IP:172.18.33.21 HOST_ID:6942404c-e512-46b4-977a-243defa48d0f LOAD:1.5512551335E10 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:ldn SEVERITY:0.0 STATUS:NORMAL,-1104014530555828728 RPC_ADDRESS:172.18.33.21 /192.168.60.133 INTERNAL_IP:192.168.60.133 HOST_ID:21d3faad-5c5d-447e-bab4-ad9323bdf4c1 LOAD:8.713849366E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.503778338432312 STATUS:NORMAL,-1040723849164479683 RPC_ADDRESS:192.168.60.133 /192.168.60.130 INTERNAL_IP:192.168.60.130 HOST_ID:3498b4b8-1047-4b42-b13b-bf27b3aa3177 LOAD:8.107882657E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.0 STATUS:NORMAL,-1011436158442308566 RPC_ADDRESS:192.168.60.130 /192.168.21.11 INTERNAL_IP:192.168.21.11 HOST_ID:dd2e69cb-232f-4236-89f2-b5479669d9f7 LOAD:1.4125019796E10 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:rdm SEVERITY:0.5128205418586731 STATUS:NORMAL,-1029672535618664309 RPC_ADDRESS:192.168.21.11 /172.18.33.23 INTERNAL_IP:172.18.33.23 HOST_ID:a08bad62-55bb-492b-be64-7cf5d5073d6d LOAD:1.2290105465E10 RELEASE_VERSION:2.0.5 NET_VERSION:7 RACK:RAC1 SCHEMA:0d9173d5-3947-328e-a14d-ce05239f61e0 DC:ldn SEVERITY:0.0 STATUS:NORMAL,-1065846071171553741 RPC_ADDRESS:172.18.33.23 /192.168.60.138 INTERNAL_IP:192.168.60.138 HOST_ID:a229bc0f-201b-479e-8312-66891f37ca85 LOAD:6.464019653E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:0.0 STATUS:NORMAL,-1091198032236176333 RPC_ADDRESS:192.168.60.138 /192.168.60.135 INTERNAL_IP:192.168.60.135 HOST_ID:860ff4bb-4fcf-43ba-b270-f1844bdd3e65 LOAD:8.112506582E9 RELEASE_VERSION:2.0.5 RACK:RAC1 NET_VERSION:7 SCHEMA:f673ced0-8cfd-3d69-baba-4f81dc60c5b5 DC:adm SEVERITY:1.5 STATUS:NORMAL,-110822321100131702 RPC_ADDRESS:192.168.60.135 schema_version of newly bootstrapped nodes disagrees with existing nodes
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919794#comment-13919794 ] Duncan Sands commented on CASSANDRA-6799: - I compared schema_columnfamilies, schema_columns and schema_keyspaces on a new and on an old node, and they are identical (schema_triggers is empty on both nodes). schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 (14 rows) I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-6799) schema_version of newly bootstrapped nodes disagrees with existing nodes
[ https://issues.apache.org/jira/browse/CASSANDRA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13919848#comment-13919848 ] Brandon Williams commented on CASSANDRA-6799: - Well, it's not a problem with the gossiped version. schema_version of newly bootstrapped nodes disagrees with existing nodes Key: CASSANDRA-6799 URL: https://issues.apache.org/jira/browse/CASSANDRA-6799 Project: Cassandra Issue Type: Bug Components: Core Environment: x86_64 ubuntu, java version 1.7.0_45, Cassandra 2.0.5 Reporter: Duncan Sands Attachments: system.log.gz After bootstrapping new nodes 172.18.33.23 and 172.18.33.24 last weekend, I noticed that they have a different schema_version to the existing nodes. The existing nodes have all been around for a while, saw some schema changes in the past (eg: timeuuid - timestamp on a column family) but none recently, and were originally running 1.2 (they were upgraded to 2.0.5). Here you see the different schema version 0d9173d5-3947-328e-a14d-ce05239f61e0 for the two nodes: cqlsh select peer, data_center, host_id, preferred_ip, rack, release_version, rpc_address, schema_version from system.peers; peer | data_center | host_id | preferred_ip | rack | release_version | rpc_address| schema_version +-+--+--+--+-++-- 192.168.21.12 | rdm | 55e4b4b6-2e64-4542-87a4-d8a8e28b5135 | null | RAC1 | 2.0.5 | 192.168.21.12 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.24 | ldn | 6e634206-94b6-4dcf-9cf8-72bfe190feee | null | RAC1 | 2.0.5 | 172.18.33.24 | 0d9173d5-3947-328e-a14d-ce05239f61e0 172.18.33.22 | ldn | 75c9c81f-b00b-4335-8483-fb7f1bc0be1e | null | RAC1 | 2.0.5 | 172.18.33.22 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.136 | adm | c83d403f-ef0d-4c54-a844-d69730fa54d3 | null | RAC1 | 2.0.5 | 192.168.60.136 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.137 | adm | b12e6d71-e189-4fe8-b00a-8ff2cc9848fd | null | RAC1 | 2.0.5 | 192.168.60.137 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.21.11 | rdm | dd2e69cb-232f-4236-89f2-b5479669d9f7 | null | RAC1 | 2.0.5 | 192.168.21.11 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.21 | ldn | 6942404c-e512-46b4-977a-243defa48d0f | null | RAC1 | 2.0.5 | 172.18.33.21 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.138 | adm | a229bc0f-201b-479e-8312-66891f37ca85 | null | RAC1 | 2.0.5 | 192.168.60.138 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.134 | adm | 7b860a54-59ea-4a92-9b47-44b52793cc70 | null | RAC1 | 2.0.5 | 192.168.60.134 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 172.18.33.23 | ldn | a08bad62-55bb-492b-be64-7cf5d5073d6d | null | RAC1 | 2.0.5 | 172.18.33.23 | 0d9173d5-3947-328e-a14d-ce05239f61e0 192.168.60.130 | adm | 3498b4b8-1047-4b42-b13b-bf27b3aa3177 | null | RAC1 | 2.0.5 | 192.168.60.130 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.133 | adm | 21d3faad-5c5d-447e-bab4-ad9323bdf4c1 | null | RAC1 | 2.0.5 | 192.168.60.133 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.135 | adm | 860ff4bb-4fcf-43ba-b270-f1844bdd3e65 | null | RAC1 | 2.0.5 | 192.168.60.135 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 192.168.60.131 | adm | d8b7b0b2-d697-43ae-ad6e-982b24637865 | null | RAC1 | 2.0.5 | 192.168.60.131 | f673ced0-8cfd-3d69-baba-4f81dc60c5b5 (14 rows) I've attached the Cassandra log showing the 172.18.33.23 node bootstrapping. -- This message was sent by Atlassian JIRA (v6.2#6252)
