Project

General

Profile

Bug #1342

Adjust/fix standby-replay configuration options, handling

Added by Greg Farnum over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Monitor
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

Description

What we'd like to see:
rename standby_replay config option to standby_for_any
Make it so that setting mds.a to standby for rank 0, and mds.as to standby for mds.a, works
Make mon_force_standby_active option only impact standby_for_any MDSes
Hopefully make it so that setting mds.a to standby for name mds.as and mds.as to standby for mds.a works

Some of this works right now, and some of it doesn't. Find out, figure out why, fix, and make the changes necessary for the rest to work.

History

#1 Updated by Greg Farnum over 8 years ago

Hmm, looking at what happens right now, I think it actually might be adequate for those who read the documentation (so, not me): http://ceph.newdream.net/wiki/Standby-replay_modes.
Right now:
The mon_force_standby_active option should only apply to those MDSes configured with "mds_standby_replay" but not with "mds_standby_for[name|rank]". There may be a bug with this under some startup orders, but it should work.
Setting mds.a to standby for mds.as, and mds.as to standby for mds.a, AND setting mds.as to "mds_standby_replay" works.
Setting mds.a to standby for rank 0, and mds.as to standby for mds.a, AND setting mds.as to "mds_standby_replay" works.

I think this allows all the scenarios one might want, and isn't any harder to configure than the goals listed above?

#2 Updated by Greg Farnum over 8 years ago

Okay, after more discussion, we just want it to work properly when you set mds.as to follow mds.a. Right now mds.as will end up in standby (rather than standby-replay) under some/all circumstances.

#3 Updated by Greg Farnum over 8 years ago

  • Category set to Monitor
  • Status changed from New to Resolved

Fixed in 9c6ec619f8ad3f88de788cf79de557c1c398274f. There was a minor bug in prepare_beacon.

Also available in: Atom PDF