Hi, The -Dbootstrap_confdir option is really only meant for a first-time bootstrap for your development environment, not for serious use.
Once you got your config into ZK you should modify the config directly in ZK. There are many tools (also 3rd party) for this. But your best choice is probably zkCli shipping with Solr. See http://wiki.apache.org/solr/SolrCloud#Command_Line_Util This means you will NOT need to start Solr with -Dboostrap_confdir at all. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 25. juni 2013 kl. 10:29 skrev Utkarsh Sengar <utkarsh2...@gmail.com>: > Hello, > > I am trying to update schema.xml for a core in a multicore setup and this > is what I do to update it: > > I have 3 nodes in my solr cluster. > > 1. Pick node1 and manually update schema.xml > > 2. Restart node1 with -Dbootstrap_conf=true > java -Dsolr.solr.home=multicore -DnumShards=3 -Dbootstrap_conf=true > -DzkHost=localhost:2181 -DSTOP.PORT=8079 -DSTOP.KEY=mysecret -jar start.jar > > 3. Restart the other 2 nodes using this command (without > -Dbootstrap_conf=true since these should pull from zk).: > java -Dsolr.solr.home=multicore -DnumShards=3 -DzkHost=localhost:2181 > -DSTOP.PORT=8079 -DSTOP.KEY=mysecret -jar start.jar > > But, when I do that. node1 displays all of my cores and the other 2 nodes > displays just one core. > > Then, I found this: > http://mail-archives.apache.org/mod_mbox/lucene-dev/201205.mbox/%3cbb7ad9bf-389b-4b94-8c1b-bbfc4028a...@gmail.com%3E > Which says bootstrap_conf is used for multicore setup. > > > But if I use bootstrap_conf for every node, then I will have to manually > update schema.xml (for any config file) everywhere? That does not sound > like an efficient way of managing configuration right? > > > -- > Thanks, > -Utkarsh
