You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2015/04/24 19:00:42 UTC

[jira] [Updated] (SOLR-7464) Cluster status API call should be served by the node which it was called from

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

Varun Thacker updated SOLR-7464:
--------------------------------
    Attachment: SOLR-7464.patch

Simple patch where cluster status is returned from the collections handler. I put all the methods which were used to get the status into a separate class called ClusterStatusAction because it was getting too big.

> Cluster status API call should be served by the node which it was called from
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-7464
>                 URL: https://issues.apache.org/jira/browse/SOLR-7464
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Varun Thacker
>            Priority: Minor
>             Fix For: Trunk, 5.2
>
>         Attachments: SOLR-7464.patch
>
>
> Currently the cluster status api call has to go to the OverseerCollectionProcessor to serve the request. We should directly serve the request from the node where the call was made to. 
> That way we will end up putting lesser tasks into the overseer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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