Hi Erick, Thanks for the response. Even I was surprised to see that behavior. Anyways I debugged it and found that Solr is not doing anything.
The flow was - Generate config locally using templates - Sync configs to remote solr servers using "rsync" <------- I started digging deeper and went through the changes done during migration from 3.x to 4.x. There was no big change except that instead of syncing only modified files, rsync was running on all the configs including tomcat's, ---localhost# rsync -v --omit-dir-times -ah --rsh .... blah blah blah ... remotehost/..... Bingo !! Tomcat was the one which was keeping track of changes in his own config/bin dirs. Once the timestamp of those dirs are changed it issued reload on all wars, resulting reload of solr cores. By the way it will be good to have a similar configurable feature in Solr. Thanks Mohit Jain On Fri, Jan 17, 2014 at 6:09 PM, Erick Erickson <erickerick...@gmail.com>wrote: > I don't think this is the case at all, but of course I could have > missed something. > That is, if by "automatically reloaded" you mean they're picked up on > server restart > or explicit core reload (see the admin API). > > But just changing the files on disk doesn't cause Solr to load the > changed configs. > > When a core reload _does_ occur, all of the relevant files are re-read. > > HTH, > Erick > > On Fri, Jan 17, 2014 at 4:47 AM, Mohit Jain <mo...@bloomreach.com> wrote: > > Hi, > > > > After upgrading Solr from 3.x to 4.x, I have observed that a solr core > gets > > automatically reloaded if a configuration file is changed. I would like > to > > know further about it > > > > - What is the flow of this feature ? > > - Is there a way to configure the set of files, so that any changes to > them > > would result in reload ? > > - Responsible classes/code ? > > > > Any pointers/help would be much appreciated. > > > > Thanks > > Mohit Jain >
