-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 11/29/18 18:53, Shawn Heisey wrote:
> On 11/29/2018 4:41 PM, Christopher Schultz wrote:
>> When mine returned (with wait=true as a request parameter), I got
>> a JSON response telling me how long it took.
>
> That's what I would expect.
>
Here's the scoop on optimize:
https://lucidworks.com/2017/10/13/segment-merging-deleted-documents-optimize-may-bad/
Note the link to how Solr 7.5 is different.
Best,
Erick
On Thu, Nov 29, 2018 at 3:53 PM Shawn Heisey wrote:
>
> On 11/29/2018 4:41 PM, Christopher Schultz wrote:
> > When mine retu
On 11/29/2018 4:41 PM, Christopher Schultz wrote:
When mine returned (with wait=true as a request parameter), I got a
JSON response telling me how long it took.
That's what I would expect.
If you have to explicitly include parameters like "wait" or
"waitSearcher" to make it block until the op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Shawn,
On 11/29/18 17:56, Shawn Heisey wrote:
> On 11/28/2018 6:22 PM, Wei wrote:
>> I use the following http request to start solr index
>> optimization:
>>
>> http://localhost:8983/solr//update?skipError=true -F
>> stream.body=' '
>>
>> The requ
On 11/28/2018 6:22 PM, Wei wrote:
I use the following http request to start solr index optimization:
http://localhost:8983/solr//update?skipError=true -F stream.body='
'
The request returns status code 200 shortly, but when looking at the solr
instance I noticed that actual optimization has not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Wei,
On 11/28/18 20:22, Wei wrote:
> Hi,
>
> I use the following http request to start solr index optimization:
>
> http://localhost:8983/solr//update?skipError=true -F
> stream.body=' '
>
>
> The request returns status code 200 shortly, but whe
Why do you think you need to optimize? Most configurations don’t need that.
And no, there is not synchronous optimize request.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Nov 28, 2018, at 6:50 PM, Zheng Lin Edwin Yeo wrote:
>
> Hi,
>
> How big
Hi,
How big is your index size, and do you have enough space in your disk to do
the optimization? You need at least twice the disk space in order for the
optimization to be successful, and even more if you are still doing
indexing during the optimization.
Also, which Solr version are you using?
