[
https://issues.apache.org/jira/browse/SOLR-12672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583935#comment-16583935
]
Trey Cahill commented on SOLR-12672:
------------------------------------
[~erickerickson], the disruptions should interrupt the entire cluster (imagine
every instance in the cluster running a stop-the-world gc at the same time), so
I'd hope that it wouldn't lead to some sort of recovery situation. I have not
tried this out on a sufficiently big cluster to verify this though.
And hopefully, there is no need to communicate to other nodes that the
disruption is occurring because every node should be disrupted (on startup, the
node will check Zookeeper for any disruptions). When disruptions are
added/removed, the request is sent to all the nodes, rather than communicated
through zookeeper (this could be a potential issue, if a single instance failed
to add a disruption becoming out of sync with the rest of the cluster).
I think [this
blog|https://blogs.apache.org/hbase/entry/medium_data_and_universal_data] will
help give a better understanding to what it's actually trying to achieve.
> 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: [email protected]
For additional commands, e-mail: [email protected]
