never keep a <str name="maxOptimizedCommitsToKeep">0</str>.
It is better to leave not mention the deletionPolicy at all. The defaults are usually fine. On Fri, Jan 22, 2010 at 11:12 AM, Stephen Weiss <swe...@stylesight.com> wrote: > Hi Shalin, > > Thanks for your reply. Please see below. > > > On Jan 18, 2010, at 4:19 AM, Shalin Shekhar Mangar wrote: > >> On Wed, Jan 13, 2010 at 12:51 AM, Stephen Weiss >> <swe...@stylesight.com>wrote: >> ... > >>> When we replicate >>> manually (via the admin page) things seem to go well. However, when >>> replication is triggered by a commit event on the master, the master gets >>> a >>> NullPointerException and no replication seems to take place. >>> >>> SEVERE: java.lang.NullPointerException >>>> >>>> at >>>> >>>> org.apache.solr.handler.ReplicationHandler$4.postCommit(ReplicationHandler.java:922) >>>> at... >>> >>> Does anyone know off the top of their head what this might indicate, or >>> know what further troubleshooting steps we should be taking to isolate >>> the >>> issue? >>> >> >> That is a strange one. It looks like the latest commit point was null. Do >> you have a deletion policy section in your solrconfig.xml? Are you always >> able to reproduce the exception? > > We are always able to reproduce the exception. > > The master has committed changes many times for over a year now... so if > that's what's being reported, it's not quite accurate. > > This is our deletion policy. I don't believe that I've edited it, it is > probably verbatim from the example (the example of what version of Solr, I > can't tell you for sure, but I imagine it's from 1.2 or 1.4 - we never > updated the config when using 1.3). > >> <deletionPolicy class="solr.SolrDeletionPolicy"> >> <str name="maxCommitsToKeep">1</str> >> <str name="maxOptimizedCommitsToKeep">0</str> >> </deletionPolicy> > > (removing comments per Noble Paul's request... we keep these in the file > for our own readability purposes but agreed, we have no need to e-mail them > along) > > I would have never thought to look there but it does seem suspicious now > that you mention it. For a proper replication configuration where we > replicate on commit, is there a recommended setting? > >>> ... >>> >> During our tests we found that enabling compression on a gigabit ethernet >> actually degrades transfer rate because of the compress/de-compress >> overhead. Just comment out that line to disable compression. > > Thank you for the clarification. We will comment it out. > > -- > Steve -- ----------------------------------------------------- Noble Paul | Systems Architect| AOL | http://aol.com
