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

When we share a cache amongst multiple stores, ensure it is only stopped once. #1118

Merged
merged 2 commits into from Nov 19, 2018

Conversation

tomwilkie
Copy link
Contributor

Fixes #1085

Signed-off-by: Tom Wilkie tom.wilkie@gmail.com

@csmarchbanks
Copy link
Contributor

Any good way to write a test for this fix/the panic?

@tomwilkie
Copy link
Contributor Author

Good call @csmarchbanks! I was wrong in my initial suggestion - its not the shared index cache (which is never stopped), but in c824ad2 we shared the chunk cache, and it was that which was failing. We don't share it anymore (after @bboreham's YAML changes).

I've changes the PR to properly stop the index cache now, which still triggers the bug. And fixes it.

Also, plumb through Stop on StorageClient, so the cachingStorageClient can stop its cache.

Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
…ped once.

Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com>
@tomwilkie tomwilkie merged commit 5d187b9 into cortexproject:master Nov 19, 2018
@tomwilkie tomwilkie deleted the 1085-stop-cache-once branch November 19, 2018 16:52
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 this pull request may close these issues.

None yet

2 participants