In this case, there's a index/core created per day. Each new day/core needs to fairly immediately after creation, replicate to the slave for queries. Is there some other mechanism in trunk/cloud that would solve this?
On Wed, Apr 28, 2010 at 9:22 AM, Yonik Seeley <yo...@lucidimagination.com> wrote: > On Wed, Apr 28, 2010 at 10:14 AM, Jason Rutherglen > <jason.rutherg...@gmail.com> wrote: >> I guess I didn't explain it properly. I want to create a core on >> the master, and then have N slaves also (aka replicate) create >> those new core(s) on the slave servers, then of course, begin to >> replicate (yeah, got that part). There doesn't appear to be >> anything today that does this, it's unclear how/if Solr Cloud >> enables the described functionality because, while yes Solr >> Cloud can be used to *create* new cores out of a config in ZK, >> that isn't what I'm asking. I'll open an issue and submit a >> patch? > > I guess the point was more that a concept of "replicating cores" > doesn't seem like the direction that Solr is currently going. So > perhaps we should back up and figure out what this new core is and why > it's being created. Is it simply a new shard (a new piece of the > whole index that shares the same config), or an entirely new > collection? > > -Yonik > Apache Lucene Eurocon 2010 > 18-21 May 2010 | Prague >
