[CASSANDRA-6799] schema_version of newly bootstrapped nodes disagrees with existing nodes

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate

Environment

x86_64 ubuntu, java version "1.7.0_45", Cassandra 2.0.5

• Severity: Normal
• Assignee: Unassigned
• Reporter: Duncan Sands
• Created: 04/Mar/14 18:47
• Updated: 16/Apr/19 09:31
• Resolved: 29/Jul/14 22:07

Description

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.

Issue Links

• duplicates: CASSANDRA-6700 Use real node messaging versions for schema exchange decisions