A regular update is a delete followed by an indexing of the document. So
technically both are indexes. :) If there's an atomic update (
https://lucene.apache.org/solr/guide/8_4/updating-parts-of-documents.html
), Solr would throw some sort of version conflict exception like
{"error":{
"metadata":[
"error-class","org.apache.solr.common.SolrException",
"root-error-class","org.apache.solr.common.SolrException"],
"msg":"version conflict for aaa expected=999999
actual=1632740120218042368",
"code":409}}
The connection refused exception does not seem related to the indexing by
itself. Maybe it has to do with you hitting the maximum connection requests
allowed per host. See in the link below the maxConnectionsPerHost and
maxConnections parameters of your Solr version:
https://lucene.apache.org/solr/guide/6_6/format-of-solr-xml.html#Formatofsolr.xml-The%3CshardHandlerFactory%3Eelement
Other than that, it can be related to connection issues with the VM,
containers, etc, I guess.
Edward
On Thu, Jan 16, 2020 at 1:45 PM rhys J <rhyssha...@gmail.com> wrote:
>
> I have noticed that if I am using curl to index a csv file *and* using
curl
> thru a script to update the Solr cores, that I get the following error:
>
> curl: (7) Failed to connect to 10.40.10.14 port 8983: Connection refused
>
> Can I only index *or* update, but not do both?
>
> I am not running shards or collections, just a standalone set of cores.
>
> Thanks,
>
> Rhys
