Well I got my answer by trying it. I issued the Collections API reload action on one of the shards (Shard4 to be exact, not the leader) and I got this back as output. So the action triggers a reload of all shards composing the Collection.
<response> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">11957</int> </lst> <lst name="success"> <lst name="Shard4:8983_solr"> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">4585</int> </lst> </lst> <lst name="Shard2:8983_solr"> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">2839</int> </lst> </lst> <lst name="Shard3:8983_solr"> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">2655</int> </lst> </lst> <lst name="Shard1:8983_solr"> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">7705</int> </lst> </lst> </lst> </response> 2014-08-27 14:00 GMT-04:00 Marc Campeau <cam...@gmail.com>: > This past thread from June might hold the answer to my question. Posting > this here for other folks that might stumble upon this question. > > ---------- Forwarded message ---------- > From: Shawn Heisey <s...@elyograg.org> > Date: 2014-06-28 1:36 GMT-04:00 > Subject: Re: Some questions about Solrcloud > To: solr-user@lucene.apache.org > > > On 6/27/2014 11:07 PM, spir...@gmail.com wrote: > > Thanks for answers ! > > > > So all my changes i'll must provide via zookeeper ? I asking because > this moment confused me when i bootstrap one node with full config, then > added 2 nodes to cluster, but conf dirs on new appended nodes is empty > (solr/collection1/conf i mean). > > > > And small question - if i bootstrap Solr with one configured core and > second core without data and default config. SolrCloud show me both cores > with replicas, how i must managed second core - add data , update configs, > via zookeeper or using Coreadmin API ? > > In my opinion, the bootstrap options should never be used. You should > upload configurations to zookeeper using the zkcli script included with > the Solr download in cloud-scripts. Then you can create collections > using the Collections API, and give the name of the config that you > uploaded earlier as a parameter. > > If you do things this way, there will be no conf directories in your > cores -- even if they exist, they are not used with SolrCloud. When you > re-upload an existing config to zookeeper to make changes, getting the > changes to take effect is as simple as using the Collections API to > RELOAD the collection. > > Thanks, > Shawn > > > > 2014-08-27 13:53 GMT-04:00 Marc Campeau <cam...@gmail.com>: > > Hi, >> >> I want to apply a change to a Schema of a Collection deployed on >> SolrCloud. >> >> This SolrCloud consists of a 3 Zookeepers ensemble overseeing 4 Solr >> Instances that each have a replicated version of a single Collection. >> >> As I understand it, I need to update my schema.xml and then upload it to >> the Zookeeper ensemble. Then I need to reload the Collection. >> >> My questions are: >> >> Do I only need to reload one Shard (Primary, anyone will do) and the >> schema update will be propagated to other shards or must I reload every >> single shard one after the other for the changes to the schema to be >> applied? >> >> Is there an order in which shards should be reloaded? >> >> Thanks for your time, >> >> Marc Campeau >> > >
