${socketTimeout:0}
>
> to
>
> ${socketTimeout:60}
>
> -Original Message-
> From: Oakley, Craig (NIH/NLM/NCBI) [C]
> Sent: Tuesday, November 19, 2019 6:19 PM
> To: solr-user@lucene.apache.org
> Subject: RE: async BACKUP under Solr8.3
>
> In some colle
For the record, the solution was to edit solr.xml changing
${socketTimeout:0}
to
${socketTimeout:60}
-Original Message-
From: Oakley, Craig (NIH/NLM/NCBI) [C]
Sent: Tuesday, November 19, 2019 6:19 PM
To: solr-user@lucene.apache.org
Subject: RE: async BACKUP under Solr8.3
In some
Sent: Tuesday, November 19, 2019 9:53 AM
To: solr-user@lucene.apache.org
Subject: RE: async BACKUP under Solr8.3
FYI, I DO succeed in doing an async backup in Solr8.1
-Original Message-
From: Oakley, Craig (NIH/NLM/NCBI) [C]
Sent: Tuesday, November 19, 2019 9:03 AM
To: solr
FYI, I DO succeed in doing an async backup in Solr8.1
-Original Message-
From: Oakley, Craig (NIH/NLM/NCBI) [C]
Sent: Tuesday, November 19, 2019 9:03 AM
To: solr-user@lucene.apache.org
Subject: RE: async BACKUP under Solr8.3
This is on a test server: simple case: one node, one shard
19, 2019 12:40 AM
To: solr-user
Subject: Re: async BACKUP under Solr8.3
Hello, Craig.
There was a significant fix for async BACKUP in 8.1, if I remember it
correctly.
Which version you used for it before? How many nodes, shards, replicas
`bug` has?
Unfortunately this stacktrace is not really
Hello, Craig.
There was a significant fix for async BACKUP in 8.1, if I remember it
correctly.
Which version you used for it before? How many nodes, shards, replicas
`bug` has?
Unfortunately this stacktrace is not really representative, it just says
that some node (ok, it's overseer) fails to wait
