New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mon/MgrMonitor: only induce mgr epoch shortly after mkfs #16356

Merged
merged 1 commit into from Jul 18, 2017

Conversation

Projects
None yet
3 participants
@liewegas
Member

liewegas commented Jul 16, 2017

For early clusters, if there isn't an active manager, we eventually want
to trigger a health warning by rolling over the mgrmap epoch. We don't
want to do that if we have no active/available manager after that. Fix
by checking ever_had_active_mgr here.

Signed-off-by: Sage Weil sage@redhat.com

mon/MgrMonitor: only induce mgr epoch shortly after mkfs
For early clusters, if there isn't an active manager, we eventually want
to trigger a health warning by rolling over the mgrmap epoch.  We don't
want to do that if we have no active/available manager after that.  Fix
by checking ever_had_active_mgr here.

Signed-off-by: Sage Weil <sage@redhat.com>

@liewegas liewegas added this to the luminous milestone Jul 16, 2017

@jcsp

jcsp approved these changes Jul 17, 2017

@tchaikov tchaikov added the needs-qa label Jul 17, 2017

@liewegas liewegas merged commit 0ff3893 into ceph:master Jul 18, 2017

4 checks passed

Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details
make check (arm64) make check succeeded
Details

@liewegas liewegas deleted the liewegas:wip-mgr-early-health branch Jul 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment