It would probable be safest just to set up a separate system as multi-core from the start, get the process working and then either use the new machine or copy the whole setup to the production machine.
Best Erick On Thu, Apr 28, 2011 at 8:49 AM, Paul Libbrecht <p...@hoplahup.net> wrote: > Just where to do I put the new index data with such a command? Simply > replacing the segment files appears dangerous to me. > > Also, what is the best practice to move from single-core to multi-core? > My current set-up is single-core, do I simply need to add a solr.xml in my > solr-home and one core1 directory with the data that was there previously? > > paul > > > Le 28 avr. 2011 à 14:04, Shaun Campbell a écrit : > >> Hi Paul >> >> Would a multi-core set up and the swap command do what you want it to do? >> >> http://wiki.apache.org/solr/CoreAdmin >> >> Shaun >> >> On 28 April 2011 12:49, Paul Libbrecht <p...@hoplahup.net> wrote: >> >>> >>> Hello list, >>> >>> I am planning to implement a setup, to be run on unix scripts, that should >>> perform a full pull-and-reindex in a background server and index then deploy >>> that index. All should happen on the same machine. >>> >>> I thought the replication methods would help me but they seem to rather >>> solve the issues of distribution while, what I need, is only the ability to: >>> >>> - suspend the queries >>> - swap the directories with the new index >>> - close all searchers >>> - reload and warm-up the searcher on the new index >>> >>> Is there a part of the replication utilities (http or unix) that I could >>> use to perform the above tasks? >>> I intend to do this on occasion... maybe once a month or even less. >>> Is "reload" the right term to be used? >>> >>> paul > >
