Solr 4.1 default commit mode

[Aditya Sakhuja <ad...@gmail.com>]

Hi,

Can someone please confirm what is the default  "commit" type for solrcloud
4.1  As per
https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConfig,
looks like softcommit is false ( which means every index update triggers an
IO ). Apparently this is application for future solrcloud 4.5.

I would appreciate if someone can confirm this for solr 4.1 ?

My second question is : Is it ok to have different commit types on
different nodes which are part of my solrCloud deployment ?

Regards,
Aditya


-- 
Regards,
-Aditya Sakhuja

Re: Solr 4.1 default commit mode

[Shawn Heisey <so...@elyograg.org>]

On 8/1/2013 3:21 PM, Aditya Sakhuja wrote:
> Can someone please confirm what is the default  "commit" type for solrcloud
> 4.1  As per
> https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConfig,
> looks like softcommit is false ( which means every index update triggers an
> IO ). Apparently this is application for future solrcloud 4.5.
>
> I would appreciate if someone can confirm this for solr 4.1 ?
>
> My second question is : Is it ok to have different commit types on
> different nodes which are part of my solrCloud deployment ?

When you send an update to Solr, commit defaults to false.  If you are 
using a software API and not constructing the URLs yourself, then the 
API might default commit to true.  The SolrJ API (for Java) that's part 
of the Solr source code does NOT default commit to true.  I have no idea 
what happens with other APIs, such as those for PHP.

Unless you (or your API) include commit=true on your update request, or 
you send an explicit commit request, a commit isn't going to happen.

When a commit actually does happen, the default is a hard commit with 
openSearcher=true.  If you want a soft commit, you must make that explicit.

Thanks,
Shawn