w this message in context:
http://n3.nabble.com/Multicore-process-tp681929p682225.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 03/28/2010 05:43 PM, Blargy wrote:
Thanks that makes perfect sense for solrconfig.xml however I dont see that
sort of functionality for solr.xml.
Im guessing Ill need to manage 2 different versions of solr.xml
Version 1 master
Version 2 slave
And my ap
sure of the exact nature of it. Im
already using the LucidKStemmer ;)
--
View this message in context:
http://n3.nabble.com/Multicore-process-tp681929p682205.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 03/28/2010 05:14 PM, Blargy wrote:
Nice. Almost there...
So it appears then that I will need two different solr.xml configurations.
One for the master defining core0 and core1 and one for the slave with the
default configuration. Is there anyway to specify master/slave specific
settings in so
ens when I have another object say "users"
http://localhost:8983/solr/users-live/replication
I guess when it comes down to that I will have to have 2 different versions
of solrconfig.xml too?
ps. I can't thank you enough for your time
--
View this message in context:
http:
On 03/28/2010 04:49 PM, Blargy wrote:
I just thought about this...
Im guessing my slaves should always be replicating from the "live" master
core: (http://localhost:8983/solr/items-live/replication).
So my master solr will have a directory structure like this:
home/items/data/core0/index
home/
and at any point the "live" core could be physically located at core0 or
core1
Whereas my slave solr will have a directory structure like this:
home/items/data/index
Is this close?
--
View this message in context:
http://n3.nabble.com/Multicore-process-tp681929p682149.html
Sent
oks like this:
home/items/data/core0/index
home/items/data/core1/index
--
View this message in context:
http://n3.nabble.com/Multicore-process-tp681929p682141.html
Sent from the Solr - User mailing list archive at Nabble.com.
Right - I'd just have the data dir be generic (like core0, core1 as you
have i example 2) and then the names will be live and offline and flip
back and forth between the core0, core1 dirs.
On 03/28/2010 04:06 PM, Blargy wrote:
Mark, first off thanks for the response. Im glad someone is around
what really matters. So Im guessing this naming convention
makes a little more sense
Sine the actually dataDir name really doesnt mean anything. Is this the
correct reasoning?
--
View this message in context:
http://n3.nabble.com/Multicore-process-tp681929p682088.html
Sent
On 03/28/2010 02:58 PM, Blargy wrote:
Also, how do I share the same schema and config files?
In solr.xml you can specify schema.xml and config.xml - just specify the
same one for each core. If you are creating cores dynamically, you can
still do this. You prob want to use the shareSchema op
On 03/28/2010 02:54 PM, Blargy wrote:
I was hoping someone could explain to me how your Solr multicore
process currently operates.
This is what I am thinking about and I was hoping I could get some
ideas/suggestions.
I have a master/slave setup where the master will be doing all the
Also, how do I share the same schema and config files?
--
View this message in context:
http://n3.nabble.com/Multicore-process-tp681929p681936.html
Sent from the Solr - User mailing list archive at Nabble.com.
I was hoping someone could explain to me how your Solr multicore process
currently operates.
This is what I am thinking about and I was hoping I could get some
ideas/suggestions.
I have a master/slave setup where the master will be doing all the indexing
via DIH. Ill be doing a full-import
14 matches
Mail list logo
