Thanks Erick, Silly oversight on my part. I went into the admin panel and used the core selector to view information about the core and it was running. I did some more thinking about it and restarted solr and looked at the core admin panel where I could see that the startTime was "-".
So the problem is operator error. I didn't think about how the core selector actually sends a query to the core to get stats, which of course starts the core. Tom On Fri, Aug 17, 2018 at 12:18 PM, Erick Erickson <erickerick...@gmail.com> wrote: > Tom: > > That hasn't been _intentionally_ changed. However, any request that > comes in (update or query) will permanently load the core (assuming no > transient cores), and any request to the core will autoload it. How > are you determining that the core hasn't been loaded? And are there > any background tasks that could be causing them to load (autowarming > in solrconfig doesn't count). > > On Fri, Aug 17, 2018 at 8:57 AM, Tom Burton-West <tburt...@umich.edu> > wrote: > > Hello, > > > > I'm not using SolrCloud and want to have some cores not load when Solr > > starts up. > > I tried loadOnStartup=false, but the cores seem to start up anyway. > > > > Is the loadOnStartup parameter still usable with Solr 6.6 or does the > > documentation need updating? > > Or Is there something else I need to do/set? > > > > Tom >
