The behavior has changed from Solr 5.0 onwards
Please refer to the "How does it work section" here https://cwiki.apache.org/confluence/display/solr/Config+API TL:DR * Every node watches the conf set directory it is using * Updating individual files WILL NOT trigger a config reload. BUt if you modify the config set dir , it will trigger a reload. This is how config API works On Mon, Apr 6, 2015 at 2:34 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/5/2015 12:32 AM, Shai Erera wrote: > > So, the questions that I have are: > > > > 1. It does look like Solr re-loads cores on configuration changes, is > > that true? > > 2. If (1) is YES, do I still need to manually invoke a collection > RELOAD > > explicitly after updating the configuration? > > 3. Can someone explain the errors I see in the log, even though the > test > > passes and as I indicated, I'm able to index more documents and > search them? > > My experience with SolrCloud is somewhat limited and even more limited > in recent versions, but it was my understanding that config/schema > changes do not result in new behavior without an explicit reload, unless > you are using the managed schema or managed resources API to make the > changes. I don't know much about how the managed APIs actually work. > > Trying to interpret the stacktraces makes my brain hurt. You probably > know a lot more about the code for those areas than I do. > > Thanks, > Shawn > > -- ----------------------------------------------------- Noble Paul
