[
https://issues.apache.org/jira/browse/SOLR-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884767#comment-15884767
]
Amrit Sarkar edited comment on SOLR-9818 at 2/26/17 3:05 PM:
-------------------------------------------------------------
The easiest way to solve this problem is to convert the *sync* ADDREPLICA call
to *async* and use REQUESTSTATUS to get the status.
In fact, we can convert all the http requests (POST/PUT) we are making using
Collections API asynchronous and ask for the status and if it fails or server
is down; don't retry and the request cycle is ended. As Ere suggested, we can
keep requesting the status until the machine gets up, but I am inclined towards
fail request and user retry the action.
See discussion on SOLR-10201, I already cooked up a patch for async CREATE
collections api.
Let me know your thoughts, I am sure this will be helpful particularly for this
issue/bug.
was (Author: sarkaramr...@gmail.com):
The easiest way to solve this problem is to convert the *sync* ADDREPLICA call
to *async* and use REQUESTSTATUS to get the status.
In fact, we can convert all the http requests we are making using Collections
API asynchronous and ask for the status and if it fails or server is down;
don't retry and the request cycle is ended. As Ere suggested, we can keep
requesting the status until the machine gets up, but I am inclined towards fail
request and user retry the action.
See discussion on SOLR-10201, I already cooked up a patch for async CREATE
collections api.
Let me know your thoughts, I am sure this will be helpful particularly for this
issue/bug.
> 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: Admin UI
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
