[
https://issues.apache.org/jira/browse/SOLR-17454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885467#comment-17885467
]
ASF subversion and git services commented on SOLR-17454:
--------------------------------------------------------
Commit 00a3bf284b6e7d3ef8941497f8dc6efacf2d4545 in solr's branch
refs/heads/main from Andrew Hankinson
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=00a3bf284b6 ]
SOLR-17454: Remove debugging error message (#2720)
Removes an errant ERROR message in the Solr logs. This message is not an error,
and since there are no other logging calls in this file, it was simply removed.
> ERROR message in logs with multithreaded searches
> -------------------------------------------------
>
> Key: SOLR-17454
> URL: https://issues.apache.org/jira/browse/SOLR-17454
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 9.7
> Environment: Solr 9.7.0
> Ubuntu 22.04 LTS
> Reporter: Andrew Hankinson
> Priority: Minor
> Labels: docs, error, log-level, multithreaded,
> pull-request-available
> Fix For: 9.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I sent a message to the Users mailing list about this, but received no
> response. However, I think it is still a problem.
> When searching with 9.7.0 and enabled multithreaded search, I now get an
> ERROR message in my logs:
> {code:java}
> 2024-09-16 08:32:05.795 ERROR (qtp1756573246-34-null-1) [c: s: r: x:core_name
> t:null-1] o.a.s.s.MultiThreadedSearcher raw read max=5922019 {code}
> The max number is the total number of documents in the core.
> I've tracked it down to this part of the code:
> [https://github.com/apache/solr/blob/5bc7c1618e05b35bd0fa8471ae09329357a82036/solr/core/src/java/org/apache/solr/search/MultiThreadedSearcher.java#L86-L91]
> I'm not entirely convinced that an ERROR level message is necessary here?
> * The query seems to still function;
> * Once the error condition is logged, the code seems to create a new doc set
> and continues;
> * The documentation doesn't suggest anything for how to avoid this? I'm not
> sure why "needDocSet" is true here, and how it can be anything otherwise?
> Surely an "info" or "warn" log message is more appropriate for these cases?
> Unless it really is an error condition, but then the docs should be updated
> to mention what could be done to avoid the error?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
