lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shawn Heisey <apa...@elyograg.org>
Subject Re: Master-Slave setup using SolrCloud
Date Thu, 02 Oct 2014 13:41:52 GMT
On 10/2/2014 6:58 AM, Sachin Kale wrote:
> We are trying to move our traditional master-slave Solr configuration to
> SolrCloud. As our index size is very small (around 1 GB), we are having
> only one shard.
> So basically, we are having same master-slave configuration with one leader
> and 6 replicas.
> We are experimenting with maxTime of both AutoCommit and AutoSoftCommit.
> Currently, autoCommit maxTime is 15 minutes and autoSoftCommit is 1 minute
> (Let me know if these values does not make sense).
> 
> Caches are set such that warmup time is at most 20 seconds.
> 
> We are having continuous indexing requests mostly for updating the existing
> documents. Few requests are for deleting/adding the documents.
> 
> The problem we are facing is that we are getting very frequent
> NullPointerExceptions.
> We get continuous 200-300 such exceptions within a period of 30 seconds and
> for next few minutes, it works fine.
> 
> Stacktrace of NullPointerException:
> 
> *ERROR - 2014-10-02 18:09:38.464; org.apache.solr.common.SolrException;
> null:java.lang.NullPointerException*
> *        at
> org.apache.solr.handler.component.QueryComponent.returnFields(QueryComponent.java:1257)*
> *        at
> org.apache.solr.handler.component.QueryComponent.handleRegularResponses(QueryComponent.java:720)*
> *        at
> org.apache.solr.handler.component.QueryComponent.handleResponses(QueryComponent.java:695)*
> 
> ‚Äč
> I am not sure what would be causing it. My guess, whenever, it is trying to
> replay tlog, we are getting these exceptions. Is anything wrong in my
> configuration?

Your automatic commit settings are fine.  If you had tried to use a very
small maxTime like 1000 (1 second), I would tell you that it's probably
too short.

The tlogs only get replayed when a core is first started or reloaded.
These appear to be errors during queries, having nothing at all to do
with indexing.

I can't be sure with the available information (no Solr version,
incomplete stacktrace, no info about what request caused and received
the error), but if I had to guess, I'd say you probably changed your
schema so that certain fields are now required that weren't required
before, and didn't reindex, so those fields are not present on every
document.  Or it might be that you added a uniqueKey and didn't reindex,
and that field is not present on every document.

http://wiki.apache.org/solr/HowToReindex

Thanks,
Shawn


Mime
View raw message