Hi Erick,
It might work. I've only worked with solr having one index on one server
over a year ago so I might need to just research more about the replication.
I am using windows and I remember that replication on windows had some
issues with scripts and hard links, however it looks like we have
Why doesn't standard replication with auto-warming work for you?
You can control how often replication gets triggered by controlling
your commit points and/or your replication interval. This seems easier
than maintaining cores like your problem statement indicates.
Best
Erick
On Fri, Aug 26, 2011
The multicore API (see http://wiki.apache.org/solr/CoreAdmin ) allows you to
swap, unload, reload cores. That should allow you to do what you want,
-Simon
On Fri, Aug 26, 2011 at 11:13 AM, Mike Austin wrote:
> I would like to have the ability to keep requests from being slowed from
> new
> docum
I would like to have the ability to keep requests from being slowed from new
document adds and commits by having a separate index that gets updated.
Basically a read-only and an updatable index. After the update index has
finished updating with new adds and commits, I'd like to switch the update
to
