[
https://issues.apache.org/jira/browse/SOLR-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585856#comment-16585856
]
Trey Cahill commented on SOLR-12672:
------------------------------------
[~elyograg],
{quote}if you ask Java for an explicit GC, it's going to be a full GC. Does
your experience align with this? {quote} - As far as I know, it does a full GC
(although IIRC, it doesn't _have to_ run a GC; it's more of a suggestion).
{quote}Are you tracking how long the System.gc() call takes in your code that
does this synchronization? {quote} - Not explicitly, but it does happen as a
side effect of scheduling the next disruption.
{quote}Do you find that explicit GCs done on a regular basis perform faster
than several seconds? {quote} - I've not looked into that; I'll work on finding
out.
{quote}If a scheduled GC does take several seconds, and this happens on every
machine in the cluster at the same time, that would be a worse problem than an
extra hundred milliseconds every now and then.{quote} - Absolutely and it'd
defeat the purpose of entire PR.
[~mbraun688], it does look like that. It seems like a commonality between
SOLR-6730 and [~varunthacker]'s suggestion is that the cluster is available the
entire time. So, rather than disrupting the entire cluster, only part of the
cluster would be affected.
> Implement Synchronized Disruption into Solr
> -------------------------------------------
>
> Key: SOLR-12672
> URL: https://issues.apache.org/jira/browse/SOLR-12672
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Trey Cahill
> Priority: Trivial
> Attachments: Synchronized Disruption in Solr.pdf
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> On large Solr clusters, at any given time, there is probably an instance
> running garbage collection. By implementing a synchronized disruption across
> the entire cluster, the response times of a large cluster should decrease as
> it helps prevent random instances from running GC while the rest of the
> cluster is responding to a request.
--
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
