You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2018/10/15 13:44:00 UTC
[jira] [Updated] (SOLR-12867) Async request status: Not getting all
status messages because a response from one node will overwrite previous
responses from that node
[ https://issues.apache.org/jira/browse/SOLR-12867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Heisey updated SOLR-12867:
--------------------------------
Description:
Problem noticed with REQUESTSTATUS on an async collections API BACKUP call.
Not all of the responses from different nodes in the collection are being reported. According to [~shalinmangar], this is because multiple responses from a node are overwriting earlier responses from that node.
Steps to reproduce:
* Start a cloud example with "bin/solr -e cloud" in a 7.5.0 binary download. Tell it that you want 3 nodes, accept defaults for all other questions.
* Create a collection with 30 shards:
** bin\solr create -c test2 -shards 30 -replicationFactor 2
* Start an async backup of the collection. On a Windows system, the URL might look like this:
** http://localhost:8983/solr/admin/collections?action=BACKUP&name=test2&collection=test2&location=C%3A%5CUsers%5Celyograg%5CDownloads%5Csolrbackups&async=sometag
* After a few seconds (to give the backup time to complete), request the status of the async operation:
** http://localhost:8983/solr/admin/collections?action=REQUESTSTATUS&requestid=sometag
The response will only contain individual statuses for 3 of the 30 shards.
was:
Problem noticed with REQUESTSTATUS on an async collections API BACKUP call.
Not all of the responses from different nodes in the collection are being reported. According to [~shalinmangar], this is because multiple responses from a node are overwriting earlier responses from that node.
> Async request status: Not getting all status messages because a response from one node will overwrite previous responses from that node
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-12867
> URL: https://issues.apache.org/jira/browse/SOLR-12867
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Shawn Heisey
> Priority: Major
>
> Problem noticed with REQUESTSTATUS on an async collections API BACKUP call.
> Not all of the responses from different nodes in the collection are being reported. According to [~shalinmangar], this is because multiple responses from a node are overwriting earlier responses from that node.
> Steps to reproduce:
> * Start a cloud example with "bin/solr -e cloud" in a 7.5.0 binary download. Tell it that you want 3 nodes, accept defaults for all other questions.
> * Create a collection with 30 shards:
> ** bin\solr create -c test2 -shards 30 -replicationFactor 2
> * Start an async backup of the collection. On a Windows system, the URL might look like this:
> ** http://localhost:8983/solr/admin/collections?action=BACKUP&name=test2&collection=test2&location=C%3A%5CUsers%5Celyograg%5CDownloads%5Csolrbackups&async=sometag
> * After a few seconds (to give the backup time to complete), request the status of the async operation:
> ** http://localhost:8983/solr/admin/collections?action=REQUESTSTATUS&requestid=sometag
> The response will only contain individual statuses for 3 of the 30 shards.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org