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

Saner defaults for configs #2344

Merged
merged 6 commits into from
Mar 30, 2020
Merged

Conversation

gouthamve
Copy link
Contributor

Signed-off-by: Goutham Veeramachaneni [email protected]

What this PR does:

Which issue(s) this PR fixes:
Fixes #

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

Signed-off-by: Goutham Veeramachaneni <[email protected]>
@bboreham
Copy link
Contributor

Seems reasonable, but I don't understand why you'd want so many tokens.
Also, what happens if you raise the number without noticing? Say you had 4 old ingesters with 128 tokens and you add a new one with 512 - does it get half the series?

@bboreham
Copy link
Contributor

Should update the docs to remove advice to set these, or at least note it's only for older versions.

Would we take these out of the example manifests?

@tomwilkie
Copy link
Contributor

Seems reasonable, but I don't understand why you'd want so many tokens.

More tokens == better load balancing - less variation is the size of the ranges owned by the ingesters.

Also, what happens if you raise the number without noticing? Say you had 4 old ingesters with 128 tokens and you add a new one with 512 - does it get half the series?

More tokens will mean more ranges, but those ranges will be smaller, so its not quite linear IIRC.

@bboreham
Copy link
Contributor

That’s a fine theory, but do we have any evidence? Has anyone ever noticed an imbalance (except me, running with 512 tokens per ingester)?

I think giving one new ingester a large fraction of the series is likely to be disastrous. Suggest this particular change should be left in the documentation.

Copy link
Contributor

@pracucci pracucci left a comment

Choose a reason for hiding this comment

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

LGTM. I left few comments, but overall looks good.

Copy link
Contributor

@bboreham bboreham left a comment

Choose a reason for hiding this comment

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

Can't set spread-flushes and leave jitter non-zero.

@bboreham
Copy link
Contributor

Do we want to remove recommendations from the docs for what is now the default?
E.g. https://github.com/cortexproject/cortex/blame/b3112b3315da58eb0ce3b50caa8df05f0a633db8/docs/guides/running.md#L244-L248

Signed-off-by: Goutham Veeramachaneni <[email protected]>
Copy link
Contributor

@bboreham bboreham left a comment

Choose a reason for hiding this comment

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

lgtm

pstibrany and others added 2 commits March 30, 2020 16:29
Signed-off-by: Goutham Veeramachaneni <[email protected]>
@gouthamve gouthamve merged commit ec3fd30 into cortexproject:master Mar 30, 2020
@gouthamve gouthamve deleted the saner-defaults branch March 30, 2020 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants