Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Subject: Re: Troubleshooting solr errors
To: solr-user@lucene.apache.org
References: <AMFES.728732b4e9.f3066d3e-772c-b276-bc91-ea7a59d30b53@amfes.com>
 <C19936F6-D17E-4600-8964-76E833CA0FDA@leirtech.com>
 <AMFES.92880a4c58.0bc54281-3004-8ad7-2d3e-07f3cebf8003@amfes.com>
From: Shawn Heisey <apache@elyograg.org>
Message-ID: <ccce701a-5124-d18c-9142-5f70e504f7da@elyograg.org>
Date: Mon, 1 May 2017 08:15:50 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <AMFES.92880a4c58.0bc54281-3004-8ad7-2d3e-07f3cebf8003@amfes.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 01 May 2017 14:16:23 -0000

On 4/25/2017 12:05 PM, Daniel Miller wrote:
> The problem isn't a particular email message - I get a cascade of
> those errors (every time a new message is received) once the server
> "breaks".  The fix is to restart the server.  I did find a Java heap
> error in the log - so I've increased the memory allocation (now to
> -Xms512m -Xmx2048m).  I had thought that a heap failure would result
> in "simple" termination - and that systemd would restart it
> appropriately - but obviously I'm missing something.

Erick covered some of this already:

The init script that the service installer script installs on a
non-windows system can start Solr, but it will not automatically restart
it if it dies.  That would require you to write something special,
probably a very custom systemd service specification, rather than use
the init script.  Automatically restarting on death is not a good idea
-- it is VERY likely that whatever caused the death is going to happen
again.

Another detail, at least on non-windows systems, is that recent Solr
versions include a script that kills the process on OutOfMemoryError
(OOME).  This is done because program operation is completely
unpredictable after that error occurs -- we have no way of knowing what
Solr will do.  There's an issue in Jira to add OOME killing to the
Windows script.

FYI, the stacktrace from an OutOfMemoryError regarding the heap is
highly unlikely to give you anything useful about why the process ran
out of memory, since *any* memory allocation in any software running in
the JVM can trigger the error.

Other errors besides OOME should never terminate Solr unless there's an
enormous bug somewhere.  That bug might be in Java itself, or even the OS.

Thanks,
Shawn