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.

Sign up for GitHub

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

Jump to bottom

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

Closed
kimchy opened this issue Jun 16, 2011 · 0 comments
Closed

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

kimchy opened this issue Jun 16, 2011 · 0 comments
Labels
>bug v0.16.3 v0.17.0

Comments

@kimchy
Copy link
Member

kimchy 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 as completed in f5fbe0d Jun 16, 2011
hibnico pushed a commit to hibnico/elasticsearch that referenced this issue Jun 27, 2011
@kimchy
River might not start properly after cluster shutdown (timing), closes …
3583f81 
…elastic#1038.
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@kimchy
River might not start properly after cluster shutdown (timing), closes …
2946903 
…elastic#1038.
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
@andsel @yaauie
Feat: Insert 'user-agent' header in requests done to the Elasticsearch (
75a4b76 
elastic#1038)

This commit adds the header `user-agent` in the form: 
logstash/<LS_version> (<OS, CPU arch, JVM details>) logstash-<plugin type>-<plugin name>/<plugin_version>
to each request passed to Elasticsearch, so that Logstash and the plugin could be identified as agent.

Co-authored-by: Ry Biesemeyer <yaauie@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.16.3 v0.17.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy