Ah, wait, my fault - I didn't have the right Solr port configured in
the slave, so snapinstaller was commiting the master :/
Thanks,
James
On 2 May 2008, at 09:17, Bill Au wrote:
snapinstall calls commit to trigger Solr to use the new index. Do
you see
the commit request in your Solr log?
snapinstall calls commit to trigger Solr to use the new index. Do you see
the commit request in your Solr log? Anything in the snapinstaller log?
Bill
On Thu, May 1, 2008 at 8:35 PM, James Brady <[EMAIL PROTECTED]>
wrote:
> Hi Ryan, thanks for that!
>
> I have one outstanding question: when I
Hi Ryan, thanks for that!
I have one outstanding question: when I take a snapshot on the master,
snappull and snapinstall on the slave, the new index is not being
used: restarting the slave server does pick up the changes, however.
Has anyone else had this problem with recent development bu
On Apr 29, 2008, at 3:09 PM, James Brady wrote:
Hi all,
I'm aiming to use the new multicore features in development versions
of Solr. My ideal setup would be to have master / slave servers on
the same machine, snapshotting across from the 'write' to the 'read'
server at intervals.
This w
Hi all,
I'm aiming to use the new multicore features in development versions
of Solr. My ideal setup would be to have master / slave servers on the
same machine, snapshotting across from the 'write' to the 'read'
server at intervals.
This was all fine with Solr 1.2, but the rsync & snappul
