[
https://issues.apache.org/jira/browse/SOLR-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Oliwa updated SOLR-8793:
-------------------------------
Comment: was deleted
(was: This problem is not fixed.
I setup a fresh Solr 6.1.0, created a core with the basic config and used curl
to push several thousand JSON files to the Solr core. In the Solr Admin UI:
WARN true LukeRequestHandler Error getting file length for [segments_1g]
java.nio.file.NoSuchFileException:
/home/user1/solr-6.1.0/server/solr/testingcore/data/index/segments_1g
at
sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
[...])
> Fix stale commit files' size computation in LukeRequestHandler
> --------------------------------------------------------------
>
> Key: SOLR-8793
> URL: https://issues.apache.org/jira/browse/SOLR-8793
> Project: Solr
> Issue Type: Bug
> Components: Server
> Affects Versions: 5.5
> Reporter: Shai Erera
> Assignee: Shai Erera
> Priority: Minor
> Fix For: 5.5.1, 6.0
>
> Attachments: SOLR-8793.patch
>
>
> SOLR-8587 added segments file information and its size to core admin status
> API. However in case of stale commits, calling that API may result on
> {{FileNotFoundException}} or {{NoSuchFileException}}, if the segments file no
> longer exists due to a new commit. We should fix that by returning a proper
> value for the file's length in this case, maybe -1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
