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

fetchCarbonsearchResponse should have retry or fallback logic #54

Open
azhiltsov opened this issue Sep 20, 2017 · 1 comment
Open

fetchCarbonsearchResponse should have retry or fallback logic #54

azhiltsov opened this issue Sep 20, 2017 · 1 comment

Comments

@azhiltsov
Copy link
Member

It either need to retry the query to carbonsearch or fail the parent query if carbonsearch fail to respond in time or carbonsearch dies in the middle of a query.
One of other options could be fallback to other carbonsearch instance (config change needed)

@azhiltsov azhiltsov changed the title fetchCarbonsearchResponse should have retry logic fetchCarbonsearchResponse should have retry or fallback logic Sep 20, 2017
@blysik
Copy link

blysik commented Sep 20, 2017

I have carbonzipper setup with essentially two sets of backends that are mirrors. It would be awesome if it would retry if one of the systems was down, and hit the mirror.

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

No branches or pull requests

2 participants