[
https://issues.apache.org/jira/browse/SOLR-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182215#comment-15182215
]
Uwe Schindler commented on SOLR-8587:
-------------------------------------
bq. How can a changing index affect the code here. The code uses an IndexReader
instance, and Lucene doesn't delete index files until the last reader is closed
(within the same process).
Lucene deletes the files no longer referenced by an index (through any commit)
so they disappear on the directory listing. IndexReaders still having them open
on older index state are not affected ("delete on last close" POSIX semantics)
- the inode is still existing, just the directory entry is gone. The inode is
deleted if nothing refers to it anymore. This is different on Windows under
some circumstances (MMapDirectory).
> 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]
