Valentin Crettaz

@softwaredoug it looks ok now after re-cloning the repo from scratch.

@dadoonet Great idea! Any plans for this?

@pentium10 we've added the following setting `action.updatebyquery.bulk_size: 50` (i.e. same size as the `queue_size` of the `bulk` queue) to the `elasticsearch.yml` config file and it works "ok" now. Another way...

Thanks @ofavre for your inputs. My apologies for not having answered sooner. I'm going to re-ingest all this and provide whatever feedback I come up with.

Compact strings are enabled by default in JDK9. I haven't tried it but it seems that behavior can be disabled by specifying `+XX:-CompactStrings` in `jvm.options`

I've come across the same issue as rompetoto and am thankful for the patch, even though I think the retry-after logic might be a bit far-fetched. tuupola, even though I...

> ...means that some subset of documents can't be indexed (if their @timestamp were to route them to that index). That's a good enough reason to prevent it IMHO... unless...

The thinking with DS (whether classic or TS) is that deletions (should) occur by means of retention settings (either via ILM or DS lifecycle). Even though it "could" make sense...

I like your "donut hole" metaphor :-) Your explanation makes sense, indeed (re snapshot restore). I still think this kind of actions should be gated in a way that the...

Very similar error on Logstash 2.1.1. Running a configuration with a `kafka` output [configured with the `avro` codec](https://www.elastic.co/guide/en/logstash/current/plugins-codecs-avro.html) ``` output { kafka { codec => { avro => { schema_uri...