${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
yes. Requeststatus is returning state=completed prematurely.
On Tuesday, 27 June 2017, Amrit Sarkar wrote:
> Damien,
>
> then I poll with REQUESTSTATUS
>
>
> REQUESTSTATUS is an API which provided you the status of the any API
> (including other heavy duty apis like SPLITSHARD or CREATECOLLECTIO
Damien,
then I poll with REQUESTSTATUS
REQUESTSTATUS is an API which provided you the status of the any API
(including other heavy duty apis like SPLITSHARD or CREATECOLLECTION)
associated with async_id at that current timestamp / moment. Does that give
you "state"="completed"?
Amrit Sarkar
Sea
A regular backup creates the files in this order:
drwxr-xr-x 2 root root 63 Jun 27 09:46 snapshot.shard7
drwxr-xr-x 2 root root 159 Jun 27 09:46 snapshot.shard8
drwxr-xr-x 2 root root 135 Jun 27 09:46 snapshot.shard1
drwxr-xr-x 2 root root 17
Yes, the async command returns, and then I poll with REQUESTSTATUS.
On 27 June 2017 at 01:24, Varun Thacker wrote:
> Hi Damien,
>
> A backup command with async is supposed to return early. It is start the
> backup process and return.
>
> Are you using the REQUESTSTATUS (
> http://lucene.apache.o
Hi Damien,
A backup command with async is supposed to return early. It is start the
backup process and return.
Are you using the REQUESTSTATUS (
http://lucene.apache.org/solr/guide/6_6/collections-api.html#collections-api
) API to validate if the backup is complete?
On Sun, Jun 25, 2017 at 10:28
11 matches
Mail list logo
