[
https://issues.apache.org/jira/browse/SOLR-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111338#comment-14111338
]
Shalin Shekhar Mangar commented on SOLR-6325:
---------------------------------------------
Yeah, you're right. I think the right place to expose index size is probably
inside the core. We should also expose the transaction log size. The patch that
I have attached here adds a "indexSizeBytes" to ReplicationHandler.
> Expose per-collection and per-shard aggregate statistics
> --------------------------------------------------------
>
> Key: SOLR-6325
> URL: https://issues.apache.org/jira/browse/SOLR-6325
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-6325.patch, SOLR-6325.patch, SOLR-6325.patch,
> SOLR-6325.patch
>
>
> SolrCloud doesn't provide any aggregate stats about the cluster or a
> collection. Very common questions such as document counts per shard, index
> sizes, request rates etc cannot be answered easily without figuring out the
> cluster state, invoking multiple core admin APIs and aggregating them
> manually.
> I propose that we expose an API which returns each of the following on a
> per-collection and per-shard basis:
> # Document counts
> # Index size on disk
> # Query request rate
> # Indexing request rate
> # Real time get request rate
> I am not yet sure if this should be a distributed search component or a
> collection API.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
