Doug, That doesn't help
-Raghu -----Original Message----- From: Doug Steigerwald [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2008 9:35 AM To: solr-user@lucene.apache.org Subject: Re: snappuller issue with multicore Try using the -d option with the snappuller so you can specify the path to the directory holding index data on local machine. Doug On Dec 10, 2008, at 10:20 AM, Kashyap, Raghu wrote: > Bill, > > Yes I do have scripts.conf for each core. However, all the options > needed for snappuller is specified in the command line itself (-D -S > etc...) > > -Raghu > > -----Original Message----- > From: Bill Au [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 10, 2008 9:17 AM > To: solr-user@lucene.apache.org > Subject: Re: snappuller issue with multicore > > I notices that you are using the same rysncd port for both core. Do > you > have a scripts.conf for each core? > > Bill > > On Tue, Dec 9, 2008 at 11:40 PM, Kashyap, Raghu > <[EMAIL PROTECTED]>wrote: > >> Hi, >> >> >> >> We are seeing a strange behavior with snappuller >> >> >> >> We have 2 cores Hotel & Location >> >> >> >> Here are the steps we perform >> >> >> >> 1. index hotel on master server >> 2. index location on master server >> 3. execute snapshooter for hotel core on master server >> 4. execute snapshooter for location core on master server >> 5. execute snappuller from slave machines (once for hotel core & >> once for location core) >> >> >> >> However, the hotel core snapshot is pulled into the location data >> dir. >> >> >> >> Here are the commands that we execute in our ruby scripts >> >> >> >> system('solr/multicore/hotel/bin/snappuller -P 18983 -S /solr/data -M >> masterServer -D /solr/data/hotel ") >> >> system("solr/multicore/location/bin/snappuller -P 18983 -M > masterServer >> -S /solr/data -D /solr/data/location") >> >> >> >> Thanks, >> >> Raghu >> >>
