I'm still in the process of reproducing the problem, so I don't have too
many details. However, I wanted to ask if anyone has faced an issue with
missing documents?
One of our .NET web services makes 2000 inserts into ElasticSearch where
the avg. document size is 20KB. On the test machine, we ended up with
50-70% of the inserted documents. I'm unable to repro the problem locally.
The setup is identical. The service also inserts the same document into SQL
and all of those end up there.
My inserts don't check for the response for higher throughput (assume that
they all make it), but I think I will need to so that I can retry. What
kind of failures messages should I look from Elastic if the insert fails?
So far, I'm only seeing success messages. For test, I'm going to negate
that and log anything I encounter.
However, I'd like to understand what the correct protocol is and why all
the documents might not be making it. The machine has 16 cores and 16 GB
memory and there are no resource issues.
Thanks,
Nick
--