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

River might not start properly after cluster shutdown (timing) #1038

kimchy opened this issue Jun 16, 2011 · 0 comments


Copy link

commented Jun 16, 2011

The retry logic to try and start a river should also handle index missing case if it has not propagated yet.

@kimchy kimchy closed this in f5fbe0d Jun 16, 2011

hibnico pushed a commit to hibnico/elasticsearch that referenced this issue Jun 27, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.