Project

General

Profile

Actions
Copy link

Bug #4765

closed

monitor: sets global version feature but upgrades might not actually have any gv data to look at

Added by Greg Farnum about 11 years ago. Updated almost 11 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
Greg Farnum
Category:
Monitor
Target version:
v0.61 - Cuttlefish
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

We don't check on doing a store conversion that we actually have GV values, only that they've been enabled on the monitor. I could see this biting somebody who tries to upgrade from argonaut to cuttlefish via a very brief bobtail run.

I'm giving this to Ian because it needs to be prioritized for real; I'm not sure how much work is involved in better handling this, nor how much we care.

Actions
Copy link
 #1

Updated by Ian Colle almost 11 years ago

  • Assignee changed from Ian Colle to Greg Farnum
  • Priority changed from Normal to Urgent
  • Target version set to v0.61 - Cuttlefish
Actions
Copy link
 #2

Updated by Greg Farnum almost 11 years ago

  • Status changed from New to Rejected

A-hah! We only need the global versions on those updates which will be involved in syncing during/following the cuttlefish upgrade; other maps can be handled as normal paxos trim (although I think there's a potential for leaking old maps without a GV, but whatever). Which means that once your monitors have formed a quorum in bobtail, they will have all the GV state they need for you to start doing upgrades.

Sorry for the false alarm. :)

Actions
Copy link

Also available in: Atom PDF