Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Subject: Re: solr shutdown
To: solr-user@lucene.apache.org
References: <104a2574-46f7-465a-72c7-6094cf067bdc@gmx.net>
 <b5c3689e-bd61-751c-2725-e546908ec4c4@elyograg.org>
From: Joe Obernberger <joseph.obernberger@gmail.com>
Message-ID: <6deb9b05-95b3-3c23-3bb0-fb05715cc9f9@gmail.com>
Date: Fri, 21 Oct 2016 12:10:50 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <b5c3689e-bd61-751c-2725-e546908ec4c4@elyograg.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Fri, 21 Oct 2016 16:10:58 -0000

Thanks Shawn - We've had to increase this to 300 seconds when using a 
large cache size with HDFS, and a fairly heavily loaded index routine (3 
million docs per day).  I don't know if that's why it takes a long time 
to shutdown, but it can take a while for solr cloud to shutdown 
gracefully.  If it does not, you end up with write.lock files for some 
(if not all) of the shards, and have to delete them manually before 
restarting.

-Joe


On 10/21/2016 9:01 AM, Shawn Heisey wrote:
> On 10/21/2016 6:56 AM, Hendrik Haddorp wrote:
>> I'm running solrcloud in foreground mode (-f). Does it make a
>> difference for Solr if I stop it by pressing ctrl-c, sending it a
>> SIGTERM or using "solr stop"?
> All of those should produce the same result in the end -- Solr's
> shutdown hook will be called and a graceful shutdown will commence.
>
> Note that in the case of the "bin/solr stop" command, the default is to
> only wait five seconds for graceful shutdown before proceeding to a
> forced kill, which for a typical install, means that forced kills become
> the norm rather than the exception.  We have an issue to increase the
> max timeout, but it hasn't been done yet.
>
> I strongly recommend anyone going into production should edit the script
> to increase the timeout.  For the shell script I would do at least 60
> seconds.  The Windows script just does a pause, not an intelligent wait,
> so going that high probably isn't advisable on Windows.
>
> Thanks,
> Shawn
>