In my case the cores are populated with different records that adhere to the same schema. The question about randomly distributing requests is because each core has the `shards` parameter populated so that it can hit the other core's indexes.
My question is more about the advantages (if any) of utilizing a dispatcher core vs. simply querying the populated cores. -- Hector On Jan 10, 2012, at 1:57 AM, shlomi java <shlomij...@gmail.com> wrote: > If you want to randomly distribute requests across shards, then I think > it's a case of Replication. > > In Replication setup, all cores have the same schema AND data, so query any > core should return the same result. It is used to support heavy load. Of > course such setup will required some kind of load balancer. > > In Distributed Search the shards have the same schema, but NOT the same > data. So there is no point of randomly querying a shard, because we will > get randomly different results. > > ShlomiJ > > On Tue, Jan 10, 2012 at 2:15 AM, Hector Castro <hectcas...@gmail.com> wrote: > >> Hi, >> >> Has anyone had success with multicore single node Solr configurations that >> have one core acting solely as a dispatcher for the other cores? For >> example, say you had 4 populated Solr cores – configure a 5th to be the >> definitive endpoint with `shards` containing cores 1-4. >> >> Is there any advantage to this setup over simply having requests >> distributed randomly across the 4 populated cores (all with `shards` equal >> to cores 1-4)? Is it even worth distributing requests across the cores >> over always hitting the same one? >> >> Thanks, >> >> -- >> Hector >> >>
