: logged correctly... on the master. I had copied scripts.conf from the
: master to all the slaves with solr_hostname=master and didn't replace
: with slave1 slave2 etc, so the commit was successful, but not on the
: slave. Dumb. Dumb.
ah ... glad we found the problem.
: Now that we are at it..
I was expecting to see the commit error which is the one that told me
before the configuration was not correct but the commit was made and
logged correctly... on the master. I had copied scripts.conf from the
master to all the slaves with solr_hostname=master and didn't replace
with slave1 slav
: problems for a few weeks, snappuller and snapinstaller run every hour
: normally, install the new index without errors etc.
:
: In the last couple of days it seems like I need to restart tomcat for
: the new documents to appear in the slave indexes. New docs are updated,
: commited and appear if
Yep, all normal..
galo
Bill Au wrote:
Did you check for error messages in the snappuller and snapinstaller
log files sunder solr/logs? Distribution related errors will not show
up in the tomcat logs.
Bill
On 4/16/07, galo <[EMAIL PROTECTED]> wrote:
Hi there,
I've been running an index on 3
Did you check for error messages in the snappuller and snapinstaller
log files sunder solr/logs? Distribution related errors will not show
up in the tomcat logs.
Bill
On 4/16/07, galo <[EMAIL PROTECTED]> wrote:
Hi there,
I've been running an index on 3 nodes (master + 2 slaves) without
proble
