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

Anshum Gupta updated SOLR-5477:
-------------------------------

    Attachment: SOLR-5477.patch

Patch with more meat. Here's what this includes:
* Request Status API based on ZK for Collection level calls.
* Request Status API for CoreAdmin level (still memory based in this patch). 
* Async mode. Specifying 'async=requestid' let's run splitshard and 
createcollection commands for now in async mode. This request id can then be 
used to track the progress of the request. If run in async mode, the call 
returns almost immediately, only pushing the task to the zk queue.
* Basic tests for the above.

Here's what's lying semi baked on my machine, will continue pushing more of 
this stuff over the next few days:
* Check and dedup the request id as specified by the user.
* CoreAdmin calls to be async from OCP in case the original call was initiated 
with 'async' option.
* Return more than just the status of the request as part of the status request 
API. Will be returning (atleast) the entire Response instead.

> Async execution of OverseerCollectionProcessor tasks
> ----------------------------------------------------
>
>                 Key: SOLR-5477
>                 URL: https://issues.apache.org/jira/browse/SOLR-5477
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>            Assignee: Anshum Gupta
>         Attachments: SOLR-5477-CoreAdminStatus.patch, SOLR-5477.patch
>
>
> Typical collection admin commands are long running and it is very common to 
> have the requests get timed out.  It is more of a problem if the cluster is 
> very large.Add an option to run these commands asynchronously
> add an extra param async=true for all collection commands
> the task is written to ZK and the caller is returned a task id. 
> as separate collection admin command will be added to poll the status of the 
> task
> command=status&id=7657668909
> if id is not passed all running async tasks should be listed
> A separate queue is created to store in-process tasks . After the tasks are 
> completed the queue entry is removed. OverSeerColectionProcessor will perform 
> these tasks in multiple threads



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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

Reply via email to