[
https://issues.apache.org/jira/browse/SOLR-13492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17070674#comment-17070674
]
Munendra S N commented on SOLR-13492:
-------------------------------------
Thanks David for the feedback. With current defaults with which we ship Solr,
jconsole and jvisualvm doesn't work as jmx is disabled by default.
Also, both the feedbacks was not add the flag. So, considering this I suggest
to go with XX:+ExplicitGCInvokesConcurrent so, explicit ones are concurrent.
I will ask [~kgsdora] to make the changes once you guys confirm
> 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
> Attachments: SOLR-13492.patch
>
> 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
