-
Notifications
You must be signed in to change notification settings - Fork 25
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 does not start after ES restart (IndexAlreadyExists Exception) #5
Comments
Ups, will have a look ... |
Same issue here. Any idea as to when this will be fixed and in which version? |
salyh
pushed a commit
that referenced
this issue
Jun 20, 2014
should be fixed with 19ba058 |
Yes, fixed! Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I restart ElasticSearch I get this message and no logs about fetching mails.
The text was updated successfully, but these errors were encountered: