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

jewel: osd: New pools have bogus stuck inactive/unclean HEALTH_ERR messages until they are first active and clean #10007

Merged
2 commits merged into from Aug 4, 2016

Commits on Jun 29, 2016

  1. osd: set pg history last_clean_scrub_stamp on create

    We were setting the other two; set this one as well.
    
    Signed-off-by: Sage Weil <sage@redhat.com>
    (cherry picked from commit 47f540d)
    liewegas authored and ldachary committed Jun 29, 2016
    Copy the full SHA
    2c03e02 View commit details
    Browse the repository at this point in the history
  2. osd/PG: set last_* PG fields on a creating PG

    Use the value from pg_history_t that ultimately came from the
    mon if last_epoch_started == 0.  This establishes a sane lower
    bound on these timestamps, and prevents a mon health error from
    coming up about how a PG is stuck in whatever state while it is
    being created.
    
    (We addressed half of this problem in commit 6ca6aea, but the
    warning comes back as soon as the OSD reports with a creating
    state.)
    
    Fixes: http://tracker.ceph.com/issues/14952
    Signed-off-by: Sage Weil <sage@redhat.com>
    (cherry picked from commit 3be3bc6)
    liewegas authored and ldachary committed Jun 29, 2016
    Copy the full SHA
    74dd035 View commit details
    Browse the repository at this point in the history