Do you see a message about idle timeout? There is a jetty bug with HTTP/2 and idle timeout that causes some stream closing. The jira below says test error, but I'm pretty sure it could come up in real usage.
* https://issues.apache.org/jira/browse/SOLR-13413 * https://github.com/eclipse/jetty.project/issues/3605 Kevin Risden On Thu, Jun 6, 2019 at 2:38 PM Erick Erickson <erickerick...@gmail.com> wrote: > Probably your packet size is too big for the Solr<->Solr default settings. > Quick test would be to try sending 10 docs per packet, then 100, then 1,000 > etc. > > There’s not much to be gained efficiency-wise once you get past 100 > docs/shard, see: > https://lucidworks.com/2015/10/05/really-batch-updates-solr-2/ > > Second, you’ll get improved throughput if you use SolrJ rather than a > straight HTTP connection, but your setup may not be amenable to that > alternative. > > Best, > Erick > > > On Jun 6, 2019, at 11:23 AM, Erie Data Systems <eriedata...@gmail.com> > wrote: > > > > Hello everyone, > > > > I recently setup Solr 8 in SolrCloud mode, previously I was using > > standalone mode and was able to easily push 10,000 records in per HTTP > call > > wit autocommit. Ingestion occurs when server A pushes (HTTPS) payload to > > server B (SolrCloud) on LAN network. > > > > However, once converted to SolrCloud (1 node, 3 shards, 1 replica) I am > > seeing the following error : > > > > ConcurrentUpdateHttp2SolrClient > > Error consuming and closing http response stream. > > > > Im wondering, what possibly causes could be, im not seeing much > > documentation online specific to Solr. > > > > Thanks in advance for any assistance, > > Craig > >
