Skip to content
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: PGMonitor: acting primary diff with cur_stat, should not set pg to stale #7083

Merged
merged 1 commit into from Jan 11, 2016

Conversation

cxwshawn
Copy link

Signed-off-by: Xiaowei Chen chen.xiaowei@h3c.com

@cxwshawn
Copy link
Author

@tchaikov yeah, if acting_primary changed, then the old primary down should not affect the pg_stat_updates, and exactly last_unstale should not change too, thanks !

@tchaikov
Copy link
Contributor

tchaikov commented Jan 4, 2016

@cxwshawn you are right, it makes sense to me. could you squash these two commit into a single one?

…ale.

Signed-off-by: Xiaowei Chen <chen.xiaowei@h3c.com>
@cxwshawn
Copy link
Author

cxwshawn commented Jan 5, 2016

@tchaikov sorry for the latency, fixed, please review, thanks.

@tchaikov
Copy link
Contributor

tchaikov commented Jan 5, 2016

lgtm with rados qa run.

liewegas added a commit that referenced this pull request Jan 11, 2016
mon: PGMonitor: acting primary diff with cur_stat, should not set pg to stale

Reviewed-by: Kefu Chai <kchai@redhat.com>
@liewegas liewegas merged commit 3df59c4 into ceph:master Jan 11, 2016
@ghost ghost changed the title PGMonitor: acting primary diff with cur_stat, should not set pg to stale. mon: PGMonitor: acting primary diff with cur_stat, should not set pg to stale Feb 10, 2016
@cxwshawn cxwshawn deleted the wip-pg_stat-fix branch February 17, 2016 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants