-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Elasticsearch output plugin is using deprecated _retry_on_conflict #9092
Comments
I've noticed the exact same behavior, is there any updates regarding this besides Jguay's workaround? |
simmel
added a commit
to simmel/logstash-output-elasticsearch
that referenced
this issue
Mar 26, 2018
simmel
added a commit
to simmel/logstash-output-elasticsearch
that referenced
this issue
Mar 27, 2018
closing as duplicate of logstash-plugins/logstash-output-elasticsearch#710 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elasticsearch deprecated logs contain the following entry for every bulk sent by logstash to ES 6.x
Add this conf and wait 10 seconds to start getting deprecated log entries
Background : If output is to ES 5.X then there will be no issue since "_retry_on_conflict" is the right setting. However when writing to ES 6.x this causes a lot of deprecated logs entries so better would be to use the new v6 setting
Workaround in case disk space issue is sparse would be to add a regex rule in log4j2.properties, this example is for standard docker ES
The text was updated successfully, but these errors were encountered: