That is probably partly because of hdfs cache key unmapping. I think I
improved that in some issue at some point.
We really want to wait by default for a long time though - even 10 minutes
or more. If you have tons of SolrCores, each of them has to be torn down,
each of them might commit on close,
thanks, I assume there is some issue on my side as I actually did not
find any of the messages that the Solr script would log out during the
shutdown. The shutdown also happened much faster then the 5 second delay
in the script. So I'm doing something wrong. Anyhow, thanks for the
further detai
bq: Would a clean shutdown result in the node to be flagged as down
in the cluster state straight away?
It should, if it's truly clean. HOWEVER. a "clean shutdown" is
unfortunately not just a "bin/solr stop" because of the timeout Shawn
mentioned, see SOLR-9371. It's a simple edit to make it
Thanks, that was what I was hoping for I just didn't see any indication
for that in the normal log output.
The reason for asking is that I have a SolrCloud 6.2.1 setup and when
ripple restarting the nodes I sometimes get errors. So far I have seen
two different things:
1) The node starts up ag
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
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
Hi,
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"?
regards,
Hendrik
On 7/2/2016 2:26 AM, Kent Mu wrote:
> I do understand your explaination, but another question accurs, When I
> create CloudSolrServer Connection by singleton pattern like this, and
> I call shutdown, but it's OK. the solr version is 4.9.0. that's why?
If SolrJ 4.9.0 allows you to call shutdown on
Thanks for your reply!
I do understand your explaination, but another question accurs, When I
create CloudSolrServer Connection by singleton pattern like this, and I
call shutdown, but it's OK. the solr version is 4.9.0. that's why?
public synchronized static CloudSolrServer getSolrCloudReadS
On 7/1/2016 10:59 PM, Kent Mu wrote:
> solr version: 4.9.0 I create and get a HttpSolrServer connection by
> singleton pattern. I find the method of "shutdown" in solrj API, so I
> decided to use "shutdown" to release resources, but I got the error as
> below, It is due to singleton pattern?
If y
hi all,
solr version: 4.9.0
I create and get a HttpSolrServer connection by singleton pattern. I find
the method of "shutdown" in solrj API, so I decided to use "shutdown" to
release resources, but I got the error as below, It is due to singleton
pattern?
*Error executing query*
*org.apache.s
hi all,
solr version: 4.9.0
I create and get a HttpSolrServer connection by singleton pattern. I find the
method of "shutdown" in solrj API, so I decided to use "shutdown" to release
resources, but I got the error as below, It is due to singleton pattern?
Error executing query
org.apache.s
12 matches
Mail list logo
