On Fri, Mar 13, 2009 at 10:33 AM, sunnyfr wrote:
> And it was obvious how during snappuller on a slave server, the query time
> was a lot longer than the rest of the time.
Did the CPU utilization drop?
It could be writing of the new files being pulled forcing parts of the
current index files out
Hi,
If the master goes down and the slave(s) already have the index, search remains
working
If the master goes down during replication, the search will remain working, but
the slave will not have/see the most recent index changes.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nu
You are welcome.
Bill
On 9/21/07, Yu-Hui Jin <[EMAIL PROTECTED]> wrote:
>
> Bill,
>
> Thanks for the explanation. That helps my understanding on rsync and the
> replication in general.
>
>
> regards,
>
> -Hui
>
> On 9/20/07, Bill Au <[EMAIL PROTECTED]> wrote:
> >
> > The "solr" that you are refer
Bill,
Thanks for the explanation. That helps my understanding on rsync and the
replication in general.
regards,
-Hui
On 9/20/07, Bill Au <[EMAIL PROTECTED]> wrote:
>
> The "solr" that you are referring to in your third question in the
> name of the rsync area which is map to the solr data dire
The "solr" that you are referring to in your third question in the
name of the rsync area which is map to the solr data directory. This
is defined in the rsyncd configuration file which is generated on the
fly as Chris has pointed out. Take a look at rsyncd-start.
snappuller rsync the index from
: So just to help my knowledge, where does this virtual setting of this "solr"
: string happen? Should it be in some config file or sth?
rsyncd-start creates an rsync config file on the fly ... much of it is
constants, but it fills in the rsync port using a variable from your
config.
-Hoss
ok. Hoss. I think I'll believe you since nobody raised any issue running the
script. And I'm about to try it out shortly with different solr home names.
So just to help my knowledge, where does this virtual setting of this "solr"
string happen? Should it be in some config file or sth?
thanks,
: home we have named. However, there's still the last part of my question
: that feels suspicious why the "solr" string is directly coded in the script
: (unlike other cases they usually use ${solr_root} to get to specific dirs.
: ) I pasted this line again below:
sorry ... i didn't realize you
Thanks, Hoss.
For the last question, yes I understand now it's referring to whatever solr
home we have named. However, there's still the last part of my question
that feels suspicious why the "solr" string is directly coded in the script
(unlike other cases they usually use ${solr_root} to get to
: 1) config different port for each solr home dir (since they run on the same
: host);
you mean a differnet rsync port right? ... yes the scripts as distributed
assume that each rsync daemon will be dedicated to a single solr
"instance" .. the idea beaing that even if you have 12 Solr intances
Ok, I should correct myself. For #1, I think we need to
1) config different port for each solr home dir (since they run on the same
host);
2) run rsync-start script under each of the solr home's bin dir.
(btw, just to make clear, we should run rsync-start after rsync-enable that
I understand.)
C
On 3/29/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
> Perhaps a future project to increase the speed of the syncing to sub-minute
> times. Sounds like two files will change, in addition to segment files being
> added. Is this correct? Or maybe other pieces such as cache reloading would
>
: Bill Au <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Wednesday, March 29, 2006 6:07:35 AM
Subject: Re: Rsync
The segments file will change when new segments are created. But what I
really
meant before was that the file deletable also
The segments file will change when new segments are created. But what I
really
meant before was that the file deletable also changes when document are
deleted from
the index.
Bill
On 3/28/06, Bill Au <[EMAIL PROTECTED]> wrote:
>
> I think the segments file will also change if documents are delet
I think the segments file will also change if documents are deleted from the
index.
Other ways to distribute the index will works as long as:
1) it makes a copy of the index that is in a consistent state
2) it keeps track of files that have changed (normally only a small amount)
and transfter th
15 matches
Mail list logo
