[
https://issues.apache.org/jira/browse/SOLR-13492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127574#comment-17127574
]
ASF subversion and git services commented on SOLR-13492:
--------------------------------------------------------
Commit aca95a1ec6a28b161e00c377e9929efbd3a9c277 in lucene-solr's branch
refs/heads/master from Guna Sekhar Dora Kovvuru
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=aca95a1 ]
SOLR-13492: perform explicit GC concurrently (#1370)
> Add ExplicitGCInvokesConcurrent by default during Solr startup
> --------------------------------------------------------------
>
> Key: SOLR-13492
> URL: https://issues.apache.org/jira/browse/SOLR-13492
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Major
> Attachments: SOLR-13492.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Solr should use the -XX:+DisableExplicitGC option as part of its default GC
> tuning.
> None of Solr's stock code uses explicit GCs, so that option will have no
> effect on most installs. The effective result of this is that if somebody
> adds custom code to Solr and THAT code does an explicit GC, it won't be
> allowed to function.
> ----
> Update: Based on the discussion in the JIRA, adding
> {{ExplicitGCInvokesConcurrent}} option instead {{DisableExplicitGC}} so that
> jcmd, jvisualvm could be run
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
