On Wed, Jan 13, 2010 at 12:51 AM, Stephen Weiss <swe...@stylesight.com>wrote:

> Hi Solr List,
>
> We're trying to set up java-based replication with Solr 1.4 (dist tarball).
>  We are running this to start with on a pair of test servers just to see how
> things go.
>
> There's one major problem we can't seem to get past.  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
>> org.apache.solr.update.UpdateHandler.callPostCommitCallbacks(UpdateHandler.java:78)
>>        at
>> org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:411)
>>
>
> 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?


>
> Also, on a (probably) unrelated topic, we're kinda confused by this section
> of the slave config:
>
>        <!--to use compression while transferring the index files. The
> possible values are internal|external
>         if the value is 'external' make sure that your master Solr has the
> settings to honour the accept-encoding header.
>         see here for details
> http://wiki.apache.org/solr/SolrHttpCompression
>         If it is 'internal' everything will be taken care of automatically.
>         USE THIS ONLY IF YOUR BANDWIDTH IS LOW . THIS CAN ACTUALLY SLOWDOWN
> REPLICATION IN A LAN-->
>        <str name="compression">internal</str>
>
> Since we *are* on a LAN, what exactly should we be doing here?  The
> language is somewhat unclear... I thought that meant that we should just
> comment out the line altogether, but others think it means that we should
> leave it set to "internal".  We get that compression is probably unnecessary
> for our more vanilla setup, we're just not 100% sure how to express that
> correctly.
>
>
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.

-- 
Regards,
Shalin Shekhar Mangar.

Reply via email to