[ https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863988#comment-13863988 ]
Anshum Gupta commented on SOLR-5477: ------------------------------------ Thanks for the inputs Hoss. Having them in zk certainly makes it easier to track completed tasks but I was just trying to 1. Keep it simpler for now 2. Have no dependency on zk for CoreAdmin tasks. Pt. 2 that I mentioned however takes a back seat if we don't intend to use it for purely core admin calls from other clients. About generating request IDs at client-side, I'll ping you on IRC and get more clarity on that. > 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 > > > 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