In fact, having a master/slave where the master is the indexing/updating machine and the slave(s) are searchers is one of the recommended configurations. The replication is used in many, many sites so it's pretty solid.
It's generally not recommended, though, to run separate instances on the *same* server. No matter how many cores/instances/etc, you're still running on the same physical hardware so I/O contention, memory issues, etc are still bounded by your hardware.... Best Erick On Thu, Dec 2, 2010 at 5:12 AM, stockii <st...@shopgate.com> wrote: > > at the time no OOM occurs. but we are not in correct live system ... > > i thougt maybe i get this problem ... > > we are running seven cores and each want be update very fast. only one core > have a huge index with 28M docs. maybe it makes sense for the future to use > solr with replication !? or can i runs two instances, one for search and > one > for updating ? or is there the danger of corrupt indizes ? > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Best-practice-for-Delta-every-2-Minutes-tp1992714p2005108.html > Sent from the Solr - User mailing list archive at Nabble.com. >
