lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Replication not working
Date Tue, 11 Jun 2013 09:51:22 GMT
Hi all,


we have a setup with multiple cores, loaded via DataImportHandlers.

Works fine so far.

Now we are trying to get the replication working (for one core so far).
But the automated replication is never happening.

Manually triggered replication works!



Solr 4.1 (also tried with 4.3)

App-Server JBoss 4.3.

Java 1.6


There are two JBoss instances running on different ports on the same box
with their own solr.home directories.


Configuration is done like described in the documentation:


<requestHandler name="/replication" class="solr.ReplicationHandler" >

         <lst name="master">

          <str name="enable">${de.der.pu.solr.master.enable:false}</str>

          <str name="replicateAfter">startup</str>

          <str name="replicateAfter">commit</str>

          <str name="replicateAfter">optimize</str>

          <str name="confFiles">stopwords.txt, solrconfig.xml</str>


         <lst name="slave">

     <str name="enable">${de.der.pu.solr.slave.enable:false}</str>


          <str name="pollInterfall">00:02:00</str>




Basically it looks all fine from the admin-pages.


The polling from the slave is going on but nothing happens.

We have tried to delete slave index completely and restart both servers.
Reimportet the master data several times and so on..


On the masters replication page I see:

- replication enable: true

- replicateAfter: commit, startup

- confFiles: stopwords.txt, solrconfig.xml


On slave side I see:

-masters version 1370612995391  53   2.56 MB

-master url:  http://localhost:30006/solr/contacts

-poling enable: true


And master settings like on master side...


When I enter
&indent=true in the browser the response seems ok:

    "indexSize":"2.56 MB",
      "confFiles":"stopwords.txt, solrconfig.xml",
  "WARNING":"This response format is experimental.  It is likely to
change in the future."}



Any idea how we could go on?





  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message