Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of bill.w.au@gmail.com
 designates 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=gl4Gz2vB4zM5/PO9K0dH/0Hua0l1zgFPXjecrMDpwIPNVFf2F5+RQLcPD6e4pgn/kI
         RDxxjdZboUGiOGl7ZQxR8Eua1KCcz+eHi5FOtjI5iZcMTyvT0nLcKaJcXckEawIJXS2/
         OBkyKJFBJG8p47hleZQ5x0FKthn0G+er3hlZk=
Message-ID: <3b5f72030807010532g70c64653q8b196c680cce945d@mail.gmail.com>
Date: Tue, 1 Jul 2008 08:32:16 -0400
From: "Bill Au" <bill.w.au@gmail.com>
To: solr-user@lucene.apache.org
Subject: Re: Rsyncd start and stop for multiple instances
In-Reply-To: <4869E19B.5020800@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22629_32073153.1214915536596"
References: <484E3A4F.8080909@gmail.com>
	 <3b5f72030806130633w603d89f6p4d68da82d3b809e5@mail.gmail.com>
	 <4869E19B.5020800@gmail.com>

------=_Part_22629_32073153.1214915536596
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You can either use a dedicated rsync port for each instance or hack the
existing scripts to support multiple rsync modules.  Both ways should work.

Bill

On Tue, Jul 1, 2008 at 3:49 AM, Jacob Singh <jacobsingh@gmail.com> wrote:

> Hi Bill and Others:
>
>
> Bill Au wrote:
> > The rsyncd-start scripts gets the data_dir path from the command line and
> > create a rsyncd.conf on the fly exporting the path as the rsync module
> named
> > "solr".  The salves need the data_dir path on the master to look for the
> > latest snapshot.  But the rsync command used by the slaves relies on the
> > rsync module name "solr" to do the file transfer using rsyncd.
>
> So is the answer that replication simply won't work for multiple
> instances unless I have a dedicated port for each one?
>
> Or is the answer that I have to hack the existing scripts?
>
> I'm a little confused when you say that slave needs to know the master's
> data dir, but, no matter what it sends, it needs to match the one known
> by the master when it starts rsyncd...
>
> Sorry if my questions are newbie, I've not actually used rsyncd, but
> I've read up quite a bit now.
>
> Thanks,
> Jacob
>
> >
> > Bill
> >
> > On Tue, Jun 10, 2008 at 4:24 AM, Jacob Singh <jacobsingh@gmail.com>
> wrote:
> >
> >> Hey folks,
> >>
> >> I'm messing around with running multiple indexes on the same server
> >> using Jetty contexts.  I've got the running groovy thanks to the
> >> tutorial on the wiki, however I'm a little confused how the collection
> >> distribution stuff will work for replication.
> >>
> >> The rsyncd-enable command is simple enough, but the rsyncd-start command
> >> takes a -d (data dir) as an argument... Since I'm hosting 4 different
> >> instances, all with their own data dirs, how do I do this?
> >>
> >> Also, you have to specify the master data dir when you are connecting
> >> from the slave anyway, so why does it need to be specified when I start
> >> the daemon?  If I just start it with any old data dir will it work for
> >> anything the user running it has perms on?
> >>
> >> Thanks,
> >> Jacob
> >>
> >
>
>

------=_Part_22629_32073153.1214915536596--