It was having multiple replicateAfter values... Perhaps a bug, though I probably won't spend time investigating the why right now, nor reproducing in the test cases.
On Tue, Jan 12, 2010 at 11:10 AM, Jason Rutherglen <jason.rutherg...@gmail.com> wrote: > Hmm...Even with the IP address in the master URL on the slave, the > indexversion command to the master mysteriously doesn't show the > latest commit... Totally freakin' bizarre! > > On Tue, Jan 12, 2010 at 10:53 AM, Jason Rutherglen > <jason.rutherg...@gmail.com> wrote: >> There's a connect exception on the client, however I'd expect this to >> show up in the slave replication console (it's not). Is this correct >> behavior (i.e. not showing replication errors)? >> >> On Mon, Jan 11, 2010 at 9:50 AM, Jason Rutherglen >> <jason.rutherg...@gmail.com> wrote: >>> Yonik, >>> >>> I added startup to replicateAfter, however no dice... There's no >>> errors the Tomcat log. >>> >>> The output of: >>> http://localhost-master:8080/solr/main/replication?command=indexversion >>> <response> >>> <lst name="responseHeader"> >>> <int name="status">0</int> >>> <int name="QTime">0</int> >>> </lst> >>> <long name="indexversion">0</long> >>> <long name="generation">0</long> >>> </response> >>> >>> The master replication UI: >>> Local Index Index Version: 1263182366335, Generation: 3 >>> Location: /mnt/solr/main/data/index >>> Size: 1.08 KB >>> >>> Master solrconfig.xml, and tomcat was restarted: >>> >>> <requestHandler name="/replication" class="solr.ReplicationHandler" > >>> <lst name="master"> >>> <str name="enable">true</str> >>> <!--Replicate on 'optimize'. Other values can be 'commit', >>> 'startup'. It is possible to have multiple entries o$ >>> <str name="replicateAfter">startup,commit,optimize</str> >>> >>> <!--Create a backup after 'optimize'. Other values can be >>> 'commit', 'startup'. It is possible to have multiple $ >>> <!-- <str name="backupAfter">optimize</str> --> >>> >>> <!--If configuration files need to be replicated give the names >>> here, separated by comma --> >>> <str >>> name="confFiles">schema.xml,synonyms.txt,stopwords.txt,elevate.xml</str> >>> <!--The default value of reservation is 10 secs.See the >>> documentation below . Normally , you should not need to$ >>> <str name="commitReserveDuration">00:10:00</str> >>> </lst> >>> </requestHandler> >>> >>> >>> On Tue, Jan 12, 2010 at 11:29 AM, Yonik Seeley >>> <yo...@lucidimagination.com> wrote: >>>> Did you try adding "startup" to the list of events to replicate after? >>>> >>>> -Yonik >>>> http://www.lucidimagination.com >>>> >>>> On Mon, Jan 11, 2010 at 12:25 PM, Jason Rutherglen >>>> <jason.rutherg...@gmail.com> wrote: >>>>> Hi, sorry for the somewhat inane question: >>>>> >>>>> I setup replication request handler on the master however I'm not >>>>> seeing any replicatable indexes via >>>>> http://localhost:8080/solr/main/replication?command=indexversion >>>>> Queries such as *:* yield results on the master (so I assume the >>>>> commit worked). The replication console shows an index, so not sure >>>>> what's going on. Here's the request handler XML on the master: >>>>> >>>>> <requestHandler name="/replication" class="solr.ReplicationHandler" > >>>>> <lst name="master"> >>>>> <str name="enable">true</str> >>>>> <!--Replicate on 'optimize'. Other values can be 'commit', >>>>> 'startup'. It is possible to have multiple entries o$ >>>>> <str name="replicateAfter">commit,optimize</str> >>>>> >>>>> <!--Create a backup after 'optimize'. Other values can be >>>>> 'commit', 'startup'. It is possible to have multiple $ >>>>> <!-- <str name="backupAfter">optimize</str> --> >>>>> >>>>> <!--If configuration files need to be replicated give the names >>>>> here, separated by comma --> >>>>> <str >>>>> name="confFiles">schema.xml,synonyms.txt,stopwords.txt,elevate.xml</str> >>>>> <!--The default value of reservation is 10 secs.See the >>>>> documentation below . Normally , you should not need to$ >>>>> <str name="commitReserveDuration">00:10:00</str> >>>>> </lst> >>>>> </requestHandler> >>>>> >>>> >>> >> >
