You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2014/03/23 08:36:44 UTC

[jira] [Resolved] (SOLR-5749) Implement an Overseer status API

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

Shalin Shekhar Mangar resolved SOLR-5749.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.8
         Assignee: Shalin Shekhar Mangar

> Implement an Overseer status API
> --------------------------------
>
>                 Key: SOLR-5749
>                 URL: https://issues.apache.org/jira/browse/SOLR-5749
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 4.8, 5.0
>
>         Attachments: SOLR-5749.patch, SOLR-5749.patch, SOLR-5749.patch, SOLR-5749.patch, SOLR-5749.patch, SOLR-5749.patch
>
>
> Right now there is little to no information exposed about the overseer from SolrCloud.
> I propose that we have an API for overseer status which can return:
> # Past N commands executed (grouped by command type)
> # Status (queue-size, current overseer leader node)
> # Overseer log



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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