[
https://issues.apache.org/jira/browse/SOLR-13492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069440#comment-17069440
]
Erick Erickson commented on SOLR-13492:
---------------------------------------
[~munendrasn] Thanks for being so thorough. I should have been more explicit, I
didn't mean to cause extra work. I don't particularly care if jconsole or
visualVM allow explicit GC, I do care that there's _some_ way to trigger GC
without restarting Solr.
So since jcmd will do the trick, I'm back to +/-0. Having to ssh over to the
machine running the Solr instance in question and executing this isn't onerous
(although I think the JDK needs to be installed). I'm still lukewarm to
protecting all Solr installations from what is a naive coding error, but
practically I don't see that it makes enough difference to argue about ;)
> Disallow explicit GC 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
> Time Spent: 20m
> 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.
--
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
