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

Preserves every sliver tool in memcache, whether it exists in monitoring data or not. #146

Merged
merged 1 commit into from
Jun 13, 2018

Conversation

nkinkade
Copy link
Contributor

@nkinkade nkinkade commented Jun 13, 2018

Currently, if a slivertool exists in mlab-ns's memcache, but does not exist in the results returned by Prometheus, it will be implicitly removed from memcache. If there is some sort of major failure in Prometheus, or a bug in our PromQL queries, that causes some or all slivertools to not be present in the monitoring data returned by a query, memcache may only know about some slivertools. If the failure is large, memcache may get close to empty and global traffic will possibly be directed at just the few remaining slivertools.

This PR ensures that all slivertools in memcache at the time the check_status cron job is run will remain in memcache, even if it means that the true status of the slivertool is unknown.


This change is Reviewable

@stephen-soltesz
Copy link
Contributor

:lgtm: -- please add a todo or create an issue to test the condition that this change should guard against.


Reviewed 1 of 1 files at r1.
Review status: 0 of 1 LGTMs obtained (and 1 stale)


Comments from Reviewable

@nkinkade
Copy link
Contributor Author

Issue created. #147.

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.

3 participants