Yes but even if I run it I've no snapshot created, I don't get how I can fixe
it.




Bill Au wrote:
> 
> You only need to run the rsync daemon on the master.
> 
> Bill
> 
> On Wed, Sep 17, 2008 at 10:54 AM, sunnyfr <[EMAIL PROTECTED]> wrote:
> 
>>
>> Hi Raghu,
>>
>> Thanks it's clear now;
>>
>>
>> Kashyap, Raghu wrote:
>> >
>> > Hi,
>> >
>> >   Rsyncd is the rsync(http://samba.anu.edu.au/rsync/)  daemon. You need
>> > to make sure that Rsynchd is running on both master & the slave
>> > machines. You use snapshooter on the master server to create the
>> > snapshot & run snappuller on the slave machines to pull those snapshots
>> > from master server and install it using the snapinstaller
>> >
>> > http://wiki.apache.org/solr/CollectionDistribution
>> >
>> > -Raghu
>> >
>> > -----Original Message-----
>> > From: sunnyfr [mailto:[EMAIL PROTECTED]
>> > Sent: Wednesday, September 17, 2008 9:11 AM
>> > To: solr-user@lucene.apache.org
>> > Subject: snappuller / rsync
>> >
>> >
>> > Hi,
>> >
>> > Sorry again,
>> > Can you please clear up a point :
>> > snappuller should be run on a slave's server to check new snapshots and
>> > pull
>> > them.
>> > and rsyncd is runned from the master.
>> >
>> > I don't get really what is rsyncd role?
>> > thanks
>> > --
>> > View this message in context:
>> > http://www.nabble.com/snappuller---rsync-tp19532941p19532941.html
>> > Sent from the Solr - User mailing list archive at Nabble.com.
>> >
>> > If you are not the intended recipient of this e-mail message, please
>> > notify the sender
>> > and delete all copies immediately. The sender believes this message and
>> > any attachments
>> > were sent free of any virus, worm, Trojan horse, and other forms of
>> > malicious code.
>> > This message and its attachments could have been infected during
>> > transmission. The
>> > recipient opens any attachments at the recipient's own risk, and in so
>> > doing, the
>> > recipient accepts full responsibility for such actions and agrees to
>> take
>> > protective
>> > and remedial action relating to any malicious code. Travelport is not
>> > liable for any
>> > loss or damage arising from this message or its attachments.
>> >
>> >
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/snappuller---rsync-tp19532941p19533954.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/snappuller---rsync-tp19532941p19605540.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to