-
Notifications
You must be signed in to change notification settings - Fork 22
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
How to bypass the cache if provider server is down and cache throws exception? #6
Comments
I guess the question is where it is supposed to be implemented/configured. Should EFCache always catch exceptions from cache provider and do the full read or is it on the provider to handle this kind of situations. |
How would you feel about setting for The number of seconds to wait after an exception before trying the cache again? |
At this point I am not planning on implementing any changes in this library except for fixing security issues. |
Is there a way to bypass the cache when the underlying cache provider is down? For example, using a remote Redis cache, if the server is not available, a call to the cache will throw an exception, which will bubble up to the caller of the DB code.
Is there a hook or a customization that we can put in place that bypasses the cache altogether on exception, so that caller doesn't have to know there was a transient error, but we can still log the exception for ops monitoring?
thanks!
The text was updated successfully, but these errors were encountered: