[
https://issues.apache.org/jira/browse/SOLR-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543022#comment-13543022
]
Markus Jelsma edited comment on SOLR-4165 at 1/3/13 4:14 PM:
-------------------------------------------------------------
We're also seeing the restarted node as ACTIVE immediately after start up in
the cluster state but it's schema and index have not been loaded yet, only
after everything is initialized the state becomes RECOVERING. Is it possible
it's ACTIVE too early so the other nodes query it but do not receive reply
until it's fully initialized?
was (Author: markus17):
We're also seeing the restarted node as ACTIVE immediately after start up
in the cloud view but it's schema and index have not been loaded yet, only
after everything is initialized the state becomes RECOVERING. Is it possible
it's active to early so the other nodes query it but do not receive reply until
it's fully initialized?
> Queries blocked when stopping and starting a node
> -------------------------------------------------
>
> Key: SOLR-4165
> URL: https://issues.apache.org/jira/browse/SOLR-4165
> Project: Solr
> Issue Type: Bug
> Components: search, SolrCloud
> Affects Versions: 5.0
> Environment: 5.0-SNAPSHOT 1366361:1420056M - markus - 2012-12-11
> 11:52:06
> Reporter: Markus Jelsma
> Priority: Critical
> Fix For: 5.0
>
>
> Our 10 node test cluster (10 shards, 20 cores) blocks incoming queries
> briefly when a node is stopped gracefully and again blocks queries for at
> least a few seconds when the node is started again.
> We're using siege to send roughly 10 queries per second to a pair a load
> balancers. Those load balancers ping (admin/ping) each node every few hundres
> milliseconds. The ping queries continue to operate normally while the
> requests to our main request handler is blocked. A manual request directly to
> a live Solr node is also blocked for the same duration.
> There are no errors logged. But it is clear that the the entire cluster
> blocks queries as soon as the starting node is reading its config from
> Zookeeper, likely even slightly earlier.
> The blocking time when stopping a node varies between 1 or 5 seconds. The
> blocking time when starting a node varies between 10 up to 30 seconds. The
> blocked queries come rushing in again after a queue of ping requests are
> served. The ping request sets the main request handler via the qt parameter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
