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

crush: update tunable docs. change default profile to jewel. #7964

Merged
merged 6 commits into from Mar 14, 2016

Conversation

liewegas
Copy link
Member

@liewegas liewegas commented Mar 8, 2016

No description provided.

Signed-off-by: Sage Weil <sage@redhat.com>
@liewegas liewegas added this to the jewel milestone Mar 8, 2016
Over time, we have made (and continue to make) improvements to the
CRUSH algorithm used to calculate the placement of data. In order to
support the change in behavior, we have introduced a series of tunable
options that control whether the legacy or improved variatio of the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean "variation"?

- break it down by tunable profile
- explicitly call out the migration impact for each profile jump.

Signed-off-by: Sage Weil <sage@redhat.com>
Signed-off-by: Sage Weil <sage@redhat.com>
Since we do not set this when we set tunables, we should not check it
when we report which tunables they have set.  For example, a savvy
operator on firefly tunables should set straw_calc_version to 1 but we
still want the cluster to report that they are on firefly tunables.

Signed-off-by: Sage Weil <sage@redhat.com>
@liewegas
Copy link
Member Author

@jecluis @athanatos will review

@athanatos
Copy link
Contributor

Ah, the min check relies on the fact that we've been choosing version names such that newer ones sort higher.

lgtm

This mimics the feature bit enforcement in OSDMap.cc but it does it based
on the version string.  This is useful when you have CRUSH tunables that
aren't mapped to a named profile.

Signed-off-by: Sage Weil <sage@redhat.com>
If they cluster is using very old tunables, as inferred by whether it
requires a newer version of CRUSH, issue a health warning.

Signed-off-by: Sage Weil <sage@redhat.com>
liewegas added a commit that referenced this pull request Mar 14, 2016
crush: update tunable docs.  change default profile to jewel

Reviewed-by: Samuel Just <sjust@redhat.com>
@liewegas liewegas merged commit 203d604 into ceph:master Mar 14, 2016
@liewegas liewegas deleted the wip-crush-jewel branch March 14, 2016 14:51
@gregsfortytwo
Copy link
Member

Make check gitbuilder has been failing since this PR merged (http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-tarball-trusty-amd64-basic/log.cgi?log=203d604d7221ac3bb721a39efff72f2f0dbb1193) — it looks to me like it's just expected output changes as a result of changing the CRUSH defaults, but definitely needs to be updated!

@tchaikov
Copy link
Contributor

@gregsfortytwo seems sage has already a PR (#8107) addressing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants