[
https://issues.apache.org/jira/browse/SOLR-13292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097141#comment-17097141
]
David Smiley commented on SOLR-13292:
-------------------------------------
This issue creates a new SolrClientCache instance on ColStatus. SCC is never
closed though. SCC ought to implement Closeable but nevertheless it implement
a close(). I think if there was a CoreContainer shared instance instead of
creating new SCC's this would be less error-prone situation.
> Provide extended per-segment status of a collection
> ---------------------------------------------------
>
> Key: SOLR-13292
> URL: https://issues.apache.org/jira/browse/SOLR-13292
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 8.0, master (9.0)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Fix For: 8.1, master (9.0)
>
> Attachments: SOLR-13292.patch, SOLR-13292.patch, adminSegments.json,
> adminSegments.json, colstatus.json, colstatus.json
>
>
> When changing a collection configuration or schema there may be non-obvious
> conflicts between existing data and the new configuration or the newly
> declared schema. A similar situation arises when upgrading Solr to a new
> version while keeping the existing data.
> Currently the {{SegmentsInfoRequestHandler}} provides insufficient
> information to detect such conflicts. Also, there's no collection-wide
> command to gather such status from all shard leaders.
> This issue proposes extending the {{/admin/segments}} handler to provide more
> low-level Lucene details about the segments, including potential conflicts
> between existing segments' data and the current declared schema. It also adds
> a new COLSTATUS collection command to report an aggregated status from all
> shards, and optionally for all collections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
