[
https://issues.apache.org/jira/browse/SOLR-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-5749:
----------------------------------------
Attachment: SOLR-5749.patch
This patch adds tracking 10 most recent failures (with entire request/response)
for each Collection API action. I think this along with the requeststatus API
added in SOLR-5477 removes the need to expose entire logs.
This can be committed now. In order to write/read stats from ZK, we need to be
able to serialize Timer and related classes. I shall do that via a different
issue.
> 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
> Fix For: 5.0
>
> Attachments: 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
