Solr 4 most definitely ignores missing cores (just run into that accidentally again myself). So, if you start Solr and directory is missing, it will survive (but complain).
The other problem is what happens when a customer deletes the account and the core directory disappears in a middle of open searcher. I would suggest some-sort of pre-delete trigger that hits Solr admin interface and unloads that core first. Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Thu, Jan 17, 2013 at 4:03 PM, Yonik Seeley <yo...@lucidworks.com> wrote: > On Thu, Jan 17, 2013 at 3:40 PM, snake <r...@michaels.me.uk> wrote: > > Ok so is there any other to stop this problem I am having where any site > > can break solr by delering their collection? > > Seems odd everyone would vote to remove a feature that would make solr > more > > stable. > > I agree. > > abortOnConfigurationError was more about a single core... if the core > would still be loaded if there were config errors. > > There *should* be a way to still load other cores if one core has an > error and is not loaded. If there's not currently, then we should > implement it. > > -Yonik > http://lucidworks.com >
