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

Supporting max item size for the memcached client (query-frontend) #3895

Closed
craigfurman opened this issue Mar 8, 2021 · 2 comments · Fixed by #3920
Closed

Supporting max item size for the memcached client (query-frontend) #3895

craigfurman opened this issue Mar 8, 2021 · 2 comments · Fixed by #3920

Comments

@craigfurman
Copy link
Contributor

craigfurman commented Mar 8, 2021

Is your proposal related to a problem?

I'm seeing error messages from the query-frontend relating to memcached insertions failing:

{
  "caller": "memcached.go:235",
  "err": "server=10.252.1.8:11211: memcache: unexpected response line from \"set\": \"SERVER_ERROR object too large for cache\r\n\"",
  "level": "error",
  "msg": "failed to put to memcached",
  "name": "",
  "ts": "2021-03-03T06:16:55.594447923Z"
}

We configure max item sizes of 16MB for both the query-range and labels caches, and set the corresponding max item size on the memcached servers.

This appears to be due to a known incomplete feature, as I also see log messages "MaxItemSize is not yet supported by the memcached client" that appear to originate from #3114. The code has a TODO above it to add this feature:

// TODO(krasi) Add support for it in the cortex module.
if config.Memcached.MaxItemSize > 0 {
level.Warn(logger).Log("message", "MaxItemSize is not yet supported by the memcached client")
}

Describe the solution you'd like

For the memcached clients used by query-frontend to support max item size.

Describe alternatives you've considered

n/a

Additional context

I don't see similar error messages from the store, for which we've deployed index and chunk memcached caches. I've only glanced at the code related to this, but the store's client doesn't appear to have this problem. We're using the default 1MB max item size there.

@craigfurman
Copy link
Contributor Author

I'm happy to try my hand at a PR for this, but figured it was worth raising first, since this appears to be an artifact of a code consolidation effort between thanos and cortex? I'm a total outsider though, and might have got the wrong end of the stick 😉

@yeya24
Copy link
Contributor

yeya24 commented Mar 8, 2021

Just opened a pr on Cortex side cortexproject/cortex#3929.
If that is merged we can support it in Thanos easily.

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

Successfully merging a pull request may close this issue.

2 participants