[ 
https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115246#comment-15115246
 ] 

Shai Erera edited comment on SOLR-8587 at 1/25/16 2:15 PM:
-----------------------------------------------------------

Oh :). But the plan is still that if the commit message starts w/ 
{{LUCENE/SOLR-XXXX}}, it will be linked to the issue, right?


was (Author: shaie):
Oh :). But the plan is still that if the commit message starts w/ 
{{LUCENE/SOLR-1234}}, it will be linked to the issue, right?

> 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, Trunk
>
>         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]

Reply via email to