[
https://issues.apache.org/jira/browse/SOLR-5477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-5477:
-----------------------------
Description:
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
was:
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
If there is a connection timeout, SolrJ assumes the node is down and re-fetch
the state for the collection and try again
> 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
>
> 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#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
