[
https://issues.apache.org/jira/browse/SOLR-12753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775612#comment-16775612
]
ASF subversion and git services commented on SOLR-12753:
--------------------------------------------------------
Commit 4aa0645ea6216f556ffd8c3ad6fcb276a0cc796d in lucene-solr's branch
refs/heads/branch_8x from erick
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=4aa0645 ]
SOLR-12055: SOLR-12753: Missed mentioning SOLR-12753 in 8.1 CHANGES.txt
> Async logging ring buffer and OOM error
> ---------------------------------------
>
> Key: SOLR-12753
> URL: https://issues.apache.org/jira/browse/SOLR-12753
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Affects Versions: 7.5
> Reporter: Andrzej Bialecki
> Assignee: Erick Erickson
> Priority: Major
> Attachments: SOLR-12753.patch
>
>
> I’m using a simulated environment for autoscaling tests, which may create
> some pretty degenerate cases (like collections with 50,000 replicas and
> Policy calculations over these, times 500 nodes).
> I noticed that when I turned on debug logging I occasionally would get an OOM
> error, and the heap dump showed that the biggest objects were a bunch of
> extremely large strings in the async logger’s ring buffer. These strings were
> admittedly extremely large (million chars or so) but the previously used sync
> logging didn’t have any issue with them, because they were consumed one by
> one.
> For sure, Solr should not attempt to be logging multi-megabyte data. But I
> also feel like the framework could perhaps help here by enforcing large but
> sane limits on maximum size of log messages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
