You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note the lack of "Got error to send bulk of actions to elasticsearch server" - from a user perspective, until I made my source modification, the entirety of my writes were erroring silently.
(This was with the version from LS 1.5.0-beta1)
(It is possible my definition of "partially fail" / "failing flush" differs from that of $author - I guess the HTTP connection was absolutely fine...)
The text was updated successfully, but these errors were encountered:
Yes, We apologize for this.
If any action within the bulk request fails, it is dropped :(
We should be pushing out the fix for this anytime now.
If you are interested in following, the PR is here: #2
In general, the update will apply the following behavior:
If an action is unsuccessful, it will be retried in the background. If it continues to fail after a certain amount of tries, it is printed out in a log message and dropped (this is the best we can do for now without extra persistence). If you have any thoughts or concerns about this policy, please let us know!
logstash-output-elasticsearch/lib/logstash/outputs/elasticsearch.rb
Lines 446 to 464 in 6860bd6
I believe that not to be the case. After changing line 449 (for debugging reasons) to:
my log looked like:
Note the lack of "Got error to send bulk of actions to elasticsearch server" - from a user perspective, until I made my source modification, the entirety of my writes were erroring silently.
(This was with the version from LS 1.5.0-beta1)
(It is possible my definition of "partially fail" / "failing flush" differs from that of $author - I guess the HTTP connection was absolutely fine...)
The text was updated successfully, but these errors were encountered: