I am using 7.0.1 without SolrCloud (sorry for missing that detail earlier).
I totally agree with you, Shawn. An crash after an OOM is not graceful like this and it usually has an incomplete logline in the end. I tried to only copy the log which seemed related to this issue, I will see if I find any other meaningful part and will copy here. On Sun, Jun 3, 2018 at 6:07 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 6/3/2018 7:52 AM, Nawab Zada Asad Iqbal wrote: > >> I am running a batch indexing job and Solr core mysteriously shut down >> without any particular error. How can I investigate this? I am focusing on >> the line which mentions "Shutting down CoreContainer instance". >> >> There are errors soon after that, but they seemed to be caused by the core >> shutting down and not the other way round; although i can be wrong. >> > > Crashes in Solr are extremely rare. If it actually does happen, it would > probably be caused by severe issues with Java or the operating system, or > hardware problems like failing memory chips. > > If you've got a recent version of Solr and it's running on an OS that's > NOT Windows, then an OutOfMemoryError is likely going to result in Solr > being killed. But if that happens, all logging stops -- Solr will not log > anything about the CoreContainer shutting down. > > The most likely cause here is that something triggered the shutdown hook > in Solr, which caused an orderly shutdown of the CoreContainer, so you got > that log message. In a nutshell, Solr shut down because something external > explicitly told it to shut down. > > Can you share the entire solr.log file? I can't guarantee that the file > will have anything in it that explains what went wrong, but we can look. > > Thanks, > Shawn > >
