You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Trey Cahill (JIRA)" <ji...@apache.org> on 2018/08/16 17:00:00 UTC
[jira] [Commented] (SOLR-12672) Implement Synchronized Disruption
into Solr
[ https://issues.apache.org/jira/browse/SOLR-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582829#comment-16582829 ]
Trey Cahill commented on SOLR-12672:
------------------------------------
I've attached a PDF presentation to explain Synchronized Disruption, it's benefits, and resources (specifically, Bloomberg's use of synchronized disruption on HBase).
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org