This is my solrj code:
UpdateRequest req = new UpdateRequest("/" + _name + "/update");
req.setAction(UpdateRequest.ACTION.OPTIMIZE, false, false);
UpdateResponse ur = req.process(_client);
The _name variable contains the name of the core, and _client is a 5.0
SolrClient, specifically HttpSolrClient. I'm trying to kick off an
optimize against a specific core without waiting for it to finish. All
my research and testing says that this is safe to do as long as the Solr
server is at least 4.0. The servers that this code runs against are
4.7.2 and 4.9.1.
This is the resulting log entry:
INFO - 2015-05-01 03:30:34.689;
org.apache.solr.update.processor.LogUpdateProcessor; [s1build]
webapp=/solr path=/update
params={optimize=true&waitSearcher=true&maxSegments=1&wt=javabin&version=2}
{optimize=} 0 2
Notice the waitSearcher=true in that log. I have set both waitFlush and
waitSearcher to false with setAction in my code. How do I successfully
start an optimize and return immediately, without waiting for it to
complete?
Thanks,
Shawn
