You probably do not need to force merge (mistakenly called "optimize") your index.
Solr does automatic merges, which work just fine. There are only a few situations where a forced merge is even a good idea. The most common one is a replicated (non-cloud) setup with a full reindex every night. If you need Solr Cloud, I cannot think of a situation where you would want a forced merge. wunder On Jul 8, 2014, at 2:01 AM, Modassar Ather <modather1...@gmail.com> wrote: > Hi, > > Need to optimize index created using CloudSolrServer APIs under SolrCloud > setup of 3 instances on separate machines. Currently it optimizes > sequentially if I invoke cloudSolrServer.optimize(). > > To make it parallel I tried making three separate HttpSolrServer instances > and invoked httpSolrServer.opimize() on them parallely but still it seems > to be doing optimization sequentially. > > I tried invoking optimize directly using HttpPost with following url and > parameters but still it seems to be sequential. > *URL* : http://host:port/solr/collection/update > > *Parameters*: > params.add(new BasicNameValuePair("optimize", "true")); > params.add(new BasicNameValuePair("maxSegments", "1")); > params.add(new BasicNameValuePair("waitFlush", "true")); > params.add(new BasicNameValuePair("distrib", "false")); > > Kindly provide your suggestion and help. > > Regards, > Modassar
