> I have increased the number of maxConnections to see if this fixes the
problem.
This solved the "connection refused" issue?
> I noticed in the log that there was an error from a curl statement that
said 'Error: Solr core is loading'
This is weird. Solr usually don't just reload cores. Are you
It doesn’t need to be identical, just anything with a buildon reload statement
> On Jan 17, 2020, at 12:17 PM, rhys J wrote:
>
> On Fri, Jan 17, 2020 at 12:10 PM David Hastings <
> hastings.recurs...@gmail.com> wrote:
>
>> something like this in your solr config:
>>
>> autosuggest > "exactMa
On Fri, Jan 17, 2020 at 12:10 PM David Hastings <
hastings.recurs...@gmail.com> wrote:
> something like this in your solr config:
>
> autosuggest "exactMatchFirst">false text str> 0.005
> DocumentDictionaryFactory title "weightField">weight true "buildOnOptimize">true
>
>
I checked both /var
something like this in your solr config:
autosuggest false text 0.005
DocumentDictionaryFactory title weight true true
On Fri, Jan 17, 2020 at 12:02 PM rhys J wrote:
> On Thu, Jan 16, 2020 at 3:48 PM David Hastings <
> hastings.recurs...@gmail.com>
> wrote:
>
> > > 'Error: Solr core is
On Thu, Jan 16, 2020 at 3:48 PM David Hastings
wrote:
> > 'Error: Solr core is loading'
>
> do you have any suggesters or anything configured that would get rebuilt?
>
>
> I don't think so? But I'm not quite sure what you are asking?
>
Rhys
> 'Error: Solr core is loading'
do you have any suggesters or anything configured that would get rebuilt?
On Thu, Jan 16, 2020 at 3:41 PM rhys J wrote:
> On Thu, Jan 16, 2020 at 3:27 PM Edward Ribeiro
> wrote:
>
> > A regular update is a delete followed by an indexing of the document. So
>
On Thu, Jan 16, 2020 at 3:27 PM Edward Ribeiro
wrote:
> 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
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":{
"metadat
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 c
