On 2/9/2017 5:24 AM, xavier jmlucjav wrote: > I always wondered, if this was not really needed, and I could just call > 'restart' in every node, in a quick loop, and forget about it. Does anyone > know if this is the case? > > My doubt is in regards to changing some config, and then doing the above > (just restart nodes in a loop). For example, what if I change a config G > used in collection C, and I restart just one of the nodes (N1), leaving the > rest alone. If all the nodes contain a shard for C, what happens, N1 is using > the new config and the rest are not? how is this handled?
If you want to change the config or schema for a collection and make it active across all nodes, just use the collections API to RELOAD the collection. The change will be picked up everywhere. https://cwiki.apache.org/confluence/display/solr/Collections+API To answer your question: No. Solr does not have the ability to restart itself. It would require significant development effort and a fundamental change in how Solr is started to make it possible. It is something that has been discussed, but at this time it is not possible. One idea that would make this possible is mentioned on the following wiki page. It talks about turning Solr into two applications instead of one: https://wiki.apache.org/solr/WhyNoWar#Information_that.27s_not_version_specific Again -- it would not be easy, which is why it hasn't been done yet. Thanks, Shawn
