Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 2 Dec 2016 09:10:58 +0000 (UTC)
From: "Ere Maijala (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.13025023.1480669754000.421555.1480669858511@Atlassian.JIRA>
In-Reply-To: <JIRA.13025023.1480669754000@Atlassian.JIRA>
References: <JIRA.13025023.1480669754000@Atlassian.JIRA> <JIRA.13025023.1480669754955@arcas>
Subject: [jira] [Updated] (SOLR-9818) Solr admin UI rapidly retries any
 request(s) if it loses connection with the server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 02 Dec 2016 09:11:00 -0000


     [ https://issues.apache.org/jira/browse/SOLR-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ere Maijala updated SOLR-9818:
------------------------------
    Summary: Solr admin UI rapidly retries any request(s) if it loses connection with the server  (was: Solr admin UI must not retry any request if it loses connection with the server)

> Solr admin UI rapidly retries any request(s) if it loses connection with the server
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-9818
>                 URL: https://issues.apache.org/jira/browse/SOLR-9818
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: web gui
>    Affects Versions: 6.3
>            Reporter: Ere Maijala
>
> It seems that whenever the Solr admin UI loses connection with the server, be the reason that the server is too slow to answer or that it's gone away completely, it starts hammering the server with the previous request until it gets a success response, it seems. That can be especially bad if the last attempted action was something like collection reload with a SolrCloud instance. The admin UI will quickly add hundreds of reload commands to overseer/collection-queue-work, which may essentially cause the replicas to get overloaded when they're trying to handle all the reload commands.
> I believe the UI should never retry the previous command blindly when the connection is lost, but instead just ping the server until it responds again.
> Steps to reproduce:
> 1.) Fire up Solr
> 2.) Open the admin UI in browser
> 3.) Open a web console in the browser to see the requests it sends
> 4.) Stop solr
> 5.) Try an action in the admin UI
> 6.) Observe the web console in browser quickly fill up with repeats of the originally attempted request


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org