[ https://issues.apache.org/jira/browse/SOLR-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sachin Goyal updated SOLR-7121: ------------------------------- Attachment: SOLR-7121.patch Added tests for long-running queries and 95th/5MinRateRequest statistics as well. GC-time test will need to run for quite sometime before it can detect the same, hence not adding test for that. But the remaining tests should provide a good testing of the patch. > Solr nodes should go down based on configurable thresholds and not rely on > resource exhaustion > ---------------------------------------------------------------------------------------------- > > Key: SOLR-7121 > URL: https://issues.apache.org/jira/browse/SOLR-7121 > Project: Solr > Issue Type: New Feature > Reporter: Sachin Goyal > Attachments: SOLR-7121.patch, SOLR-7121.patch, SOLR-7121.patch, > SOLR-7121.patch, SOLR-7121.patch > > > Currently, there is no way to control when a Solr node goes down. > If the server is having high GC pauses or too many threads or is just getting > too many queries due to some bad load-balancer, the cores in the machine keep > on serving unless they exhaust the machine's resources and everything comes > to a stall. > Such a slow-dying core can affect other cores as well by taking huge time to > serve their distributed queries. > There should be a way to specify some threshold values beyond which the > targeted core can its ill-health and proactively go down to recover. > When the load improves, the core should come up automatically. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org