[
https://issues.apache.org/jira/browse/SOLR-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15701538#comment-15701538
]
Tim Owen commented on SOLR-8793:
--------------------------------
We get this using Solr 6.3.0 because it's still logged at WARN level, which
seems a bit alarmist to me. For indexes that are changing rapidly, it happens a
lot. We're going to increase our logging threshold for that class to ERROR,
because these messages are just filling up the logs and there's no action we
can actually take to prevent it, because they're expected to happen sometimes.
Personally I would make this message INFO level.
> 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
