lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anshum Gupta (JIRA)" <>
Subject [jira] [Updated] (SOLR-5477) Async execution of OverseerCollectionProcessor tasks
Date Fri, 24 Jan 2014 20:44:42 GMT


Anshum Gupta updated SOLR-5477:

    Attachment: SOLR-5477.patch

Added checking for existing tasks with the same id.

Have a lot of coming up in the logs. Trying to debug that.

414075 [Overseer-91131269805768705-] WARN
 – Overseer cannot talk to ZK
414075 [Thread-16] ERROR  – Exception in Overseer main queue
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
for /overseer/queue...

> Async execution of OverseerCollectionProcessor tasks
> ----------------------------------------------------
>                 Key: SOLR-5477
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>            Assignee: Anshum Gupta
>         Attachments: SOLR-5477-CoreAdminStatus.patch, SOLR-5477.patch, SOLR-5477.patch,
SOLR-5477.patch, SOLR-5477.patch, SOLR-5477.patch, SOLR-5477.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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message