<p dir="auto">When using the bulk API with <em>a lot</em> of documents (say 100K), it's kind of pointless to get a response for each of those documents because the response is huge! Cannot we have a way to call this API and only receive a response that is either:</p>
<ul dir="auto">
<li>Successful insertion of all documents (count).</li>
<li>Some insertion failed (count of the ones that failed).</li>
<li>All insertion failed (count).</li>
</ul>
<p dir="auto">I know that I could probably use Bulk UDP (and I'll probably give it a go soon), but UDP doesn't receive any response whatsoever, so it's like having black&amp;white, but not any shade of grey.</p>
<p dir="auto">Thanks!</p>
<p dir="auto"><strong>Elasticsearch version</strong>: 2.3.1</p>
<p dir="auto"><strong>JVM version</strong>:8u77</p>
<p dir="auto"><strong>OS version</strong>:OL 7u1 and Solaris 11.2</p>
<p dir="auto"><strong>Description of the problem including expected versus actual behavior</strong>:<br>
Cluster is operating normally and runs into an out of space condition on a node, that is the 85% value is reached. Shard stays in initializing state and following does not clear the condition.</p>
<ol dir="auto">
<li>Attempts to reassign ( Message below)</li>
<li>Reboots of nodes with shard having issue resident</li>
<li>Change of replicas from 4 to 2</li>
</ol>
<p dir="auto"><strong>Steps to reproduce</strong>:</p>
<ol dir="auto">
<li>Run a cluster and fill up the disk on some node</li>
<li>Have other indices with continuous writes</li>
<li>wait until shards start showing unassigned</li>
</ol>
<p dir="auto"><strong>Provide logs (if relevant)</strong>:</p>
<p dir="auto">2016-04-19 22:32:35] {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"[move_allocation] can't move [logstash-feeder-df-2016.04][1], shard is not started (state = INITIALIZING]"}],"type":"illegal_argument_exception","reason":"[move_allocation] can't move [logstash-feeder-df-2016.04][1], shard is not started (state = INITIALIZING]"},"status":400}</p>