Project

General

Profile

Actions
Copy link

Bug #2690

closed

mon: persist quorum features

Added by Sage Weil almost 12 years ago. Updated over 10 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
Monitor
Target version:
-
% Done:

0%

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

Description

currently the non-leaders do not know the quorum features, and encode everything with a minimal (0) feature set.

i think they should encode using the last known quorum feature set. this will mean that once a quorum is established that has a new feature data will start to be encoded with it, and going backwards will lead to trouble (which is unavoidable, i think).

Actions
Copy link
 #1

Updated by Sage Weil almost 12 years ago

  • Backport set to argonaut
Actions
Copy link
 #2

Updated by Sage Weil almost 12 years ago

  • Target version deleted (v0.50)
Actions
Copy link
 #3

Updated by Sage Weil almost 12 years ago

  • Priority changed from High to Normal
Actions
Copy link
 #4

Updated by Sage Weil over 10 years ago

  • Status changed from 12 to Won't Fix

we should use compatset features in cases where this is unsafe.

Actions
Copy link

Also available in: Atom PDF