[
https://issues.apache.org/jira/browse/SOLR-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077125#comment-18077125
]
ASF subversion and git services commented on SOLR-18202:
--------------------------------------------------------
Commit a484172a97d39441bddc8af85eff702856dcc2ba in solr's branch
refs/heads/main from Luke Kot-Zaniewski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a484172a97d ]
SOLR-18202 Reduce Memory Usage of testSequentialVsParallelFingerprint (#4310)
testSequentialVsParallelFingerprint creates a bunch of segments by design. This
creates enormous memory overhead, partly because a new searcher is opened with
each commit.
I tried setting openSearcher to false but the RealtimeGetHandler searcher still
gets opened and incurs similar memory overhead per commit. I landed on just
writing via IW which seems ok for this test. For reference by doing this we
reduce the total memory consumption of this test by about 10-20X according to
my profiler.
> Scary uptick in failures from SolrIndexFingerprintTest (OOM risk)
> -----------------------------------------------------------------
>
> Key: SOLR-18202
> URL: https://issues.apache.org/jira/browse/SOLR-18202
> Project: Solr
> Issue Type: Test
> Reporter: Chris M. Hostetter
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> * SolrIndexFingerprintTest was added to the (main branch) Solr codebase by
> SOLR-17756 ~ 2025-05-21
> ** it has always had a single test method:
> testSequentialVsParallelFingerprint
> * [Historical jenkins
> metrics|https://fucit.org/solr-jenkins-reports/history-trend-of-recent-failures.html#series/org.apache.solr.update.SolrIndexFingerprintTest.testSequentialVsParallelFingerprint]
> show that for the first ~3 months this test existed, it had a consistent
> (weekly) failure rate of 0%
> * Starting sometime just before ~ 2025-08-25, the weekly failure rate
> started to fluctuate between 0-3%
> ** This date corresponds with the changes introduced by SOLR-17863
> * Sometime during the week ending 2026-03-30, the weekly jenkins failure
> rate jumpted to ~ 10%, and seems to be staying there
> ** spot checking the logs of recent jenkins failures, the recent errors all
> seem to be OOM related.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
