[
https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182185#comment-15182185
]
Shai Erera commented on SOLR-8587:
----------------------------------
I've just tried that on 5.5.0 and it seems to work without any problems. I did
use {{bin/solr start -e cloud}} and not on a "real" Solr box though (haven't
upgraded them to 5.5 yet), but I don't see how this exception is possible. The
code uses an instance of {{IndexReader}} to get all that information, and that
instance must have read the {{segments_N}} to read the commit point. Could
there be some other process on that may delete this file?
> Add segments file information to core admin status
> --------------------------------------------------
>
> Key: SOLR-8587
> URL: https://issues.apache.org/jira/browse/SOLR-8587
> Project: Solr
> Issue Type: Improvement
> Reporter: Shai Erera
> Assignee: Shai Erera
> Fix For: 5.5, master
>
> Attachments: SOLR-8587.patch, SOLR-8587.patch
>
>
> Having the index's segments file name returned by CoreAdminHandler STATUS can
> be useful. The info I'm thinking about is the segments file name and its
> size. If you record that from time to time, in a case of crisis, when u need
> to restore the index and may not be sure which copy you need to restore, this
> tiny piece of info can be very useful, as the segmentsN file records the
> commit point, and therefore what you core reported and what you see at hand
> can help you make a safer decision.
> I also think it's useful info in general, e.g. probably even more than
> 'version', and it doesn't add much complexity to the handler or the response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
