Project

General

Profile

Bug #20949

mon: quorum incorrectly believes mon has kraken (not jewel) features

Added by Sage Weil about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
08/08/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:

Description

mon.2 is the last mon to restart:

2017-08-08 19:53:35.622533 7f3d1afea700  1 -- 172.21.15.53:6791/0 _send_message--> mon.0 172.21.15.53:6789/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 ack 9) v6 -- ?+0 0x7f3d2d1fcec0
2017-08-08 19:53:35.622552 7f3d1afea700  1 -- 172.21.15.53:6791/0 --> 172.21.15.53:6789/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 ack 9) v6 -- 0x7f3d2d1fcec0 con 0
2017-08-08 19:53:35.622691 7f3d1cfee700 10 _calc_signature seq 320379555 front_crc_ = 2642237895 middle_crc = 0 data_crc = 0 sig = 14435986602495221758
2017-08-08 19:53:35.622707 7f3d1cfee700 20 Putting signature in client message(seq # 320379555): sig = 14435986602495221758
2017-08-08 19:53:35.859682 7fb24f410e00 -1 WARNING: all dangerous and experimental features are enabled.
2017-08-08 19:53:35.859711 7fb24f410e00  0 ceph version 12.1.2-452-g5260977 (52609778251859dc3d9ab17333d5abc2822c1a00) luminous (rc), process (unknown), pid 19337
2017-08-08 19:53:35.861190 7fb24f410e00 -1 WARNING: all dangerous and experimental features are enabled.

it kraken mon acks right before it restarts... and when the new luminous mon comes up, it joins the same election cycle:
2017-08-08 19:53:35.999515 7fb243c93700  5 mon.c@2(electing).elector(0) start -- can i be leader?
2017-08-08 19:53:35.999626 7fb243c93700  1 mon.c@2(electing).elector(9) init, last seen epoch 9
2017-08-08 19:53:36.026056 7fb243c93700  1 -- 172.21.15.53:6791/0 _send_message--> mon.0 172.21.15.53:6789/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 propose 9) v7 -- ?+0 0x7fb2583449c0
2017-08-08 19:53:36.026073 7fb243c93700  1 -- 172.21.15.53:6791/0 --> 172.21.15.53:6789/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 propose 9) v7 -- 0x7fb2583449c0 con 0
2017-08-08 19:53:36.026096 7fb243c93700  1 -- 172.21.15.53:6791/0 _send_message--> mon.1 172.21.15.53:6790/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 propose 9) v7 -- ?+0 0x7fb258345040
2017-08-08 19:53:36.026103 7fb243c93700  1 -- 172.21.15.53:6791/0 --> 172.21.15.53:6790/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 propose 9) v7 -- 0x7fb258345040 con 0
...
2017-08-08 19:53:36.076683 7fb243c93700  5 mon.c@2(electing).elector(9) handle_propose from mon.1
2017-08-08 19:53:36.076686 7fb243c93700 10 mon.c@2(electing).elector(9) handle_propose required features 153140804150378496 mon_feature_t([kraken]), peer features 2305244844532236283 mon_feature_t([kraken,luminous])
2017-08-08 19:53:36.076695 7fb243c93700  5 mon.c@2(electing).elector(9) defer to 1
2017-08-08 19:53:36.076938 7fb243c93700  1 -- 172.21.15.53:6791/0 _send_message--> mon.1 172.21.15.53:6790/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 ack 9) v7 -- ?+0 0x7fb258344d00
2017-08-08 19:53:36.076955 7fb243c93700  1 -- 172.21.15.53:6791/0 --> 172.21.15.53:6790/0 -- election(d09ca05f-a218-4e14-9b62-4a9da8defe78 ack 9) v7 -- 0x7fb258344d00 con 0
2017-08-08 19:53:36.077032 7fb24749a700 10 _calc_signature seq 4 front_crc_ = 88716647 middle_crc = 0 data_crc = 0 sig = 893230251600686018
2017-08-08 19:53:36.077044 7fb24749a700 20 Putting signature in client message(seq # 4): sig = 893230251600686018
2017-08-08 19:53:36.185040 7fb24849c700 10 _calc_signature seq 1665379444 front_crc_ = 1953855680 middle_crc = 0 data_crc = 0 sig = 13613875224185471080
2017-08-08 19:53:36.185079 7fb243c93700  1 -- 172.21.15.53:6791/0 <== mon.0 172.21.15.53:6789/0 1665379444 ==== election(d09ca05f-a218-4e14-9b62-4a9da8defe78 victory 10) v7 ==== 42583+0+0 (1953855680 0 0) 0x7fb2583449c0 con 0x7fb2584c2800
2017-08-08 19:53:36.185116 7fb243c93700 20 mon.c@2(electing) e2 _ms_dispatch existing session 0x7fb257f2ec00 for mon.0 172.21.15.53:6789/0
2017-08-08 19:53:36.185126 7fb243c93700 20 mon.c@2(electing) e2  caps allow *

but note that the second (luminous) ack it sent is ignored; it's the first one that the leader uses:
2017-08-08 19:53:36.160851 7f453afb8700  5 mon.a@0(electing).elector(9)  so far i have { mon.0: features 2305244844532236283 mon_feature_t([kraken,luminous]), mon.1: features 2305244844532236283 mon_feature_t([kraken,luminous]), mon.2: features 1152323339923292155 mon_feature_t([kraken]) }

/a/sage-2017-08-08_18:13:58-upgrade:kraken-x-luminous-distro-basic-smithi/1497724

History

#1 Updated by Sage Weil about 2 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF