Practical Use-Cases of Solr's AutoScaling Framework #bbuzz
summary
Solr’s AutoScaling framework aims to let clusters grow to a trillion documents with minimal ops effort by using declarative policies (hard rules) and preferences (load sorting), a diagnostics API, and event-driven triggers. It adds features like auto add replicas to maintain replication after node loss, and a search rate trigger (Solr 7.3) that computes plans to add or move replicas based on QPS before optionally executing them. Experimentally killing a node keeps replication and respects AZ placement; triggers can notify via HTTP and can compute plans without auto-executing for manual validation.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:30Why Auto-Scaling?
- 2:19In a nutshell
- 2:48Describing your cluster
- 4:40Auto-Scaling Policies
- 8:04Auto-Scaling Policy - API
- 8:22Auto-Scaline Preferences
- 12:32Auto-Scaling Preferences - API
- 14:54Collection APIs
- 17:04Collection Replication Factor
- 22:10Auto-Scaling Triggers - API
- 25:37Search Rate Trigger - API
- 26:40Trigger Actions
- 30:34Trigger Listener
related talks
31mAutoscaling: the why, what, how & when to help you implement it
16mAutoscaling Distributed System with BOSH
36mAutoscaling Search and Analytics in Kubernetes: The OpenSearch Operator Advantage
08mSolr Cloud Manager
44mRiak, Redis, Apache Solr & Spark: Deploying with the Basho Data Platform
46mOperating an OpenSearch Powered E-commerce Search Engine at Scale
52mOperating OpenSearch at Scale: Lessons From Managing 10,000+ Clusters Across...
28mAutomated Deployment of ElasticSearch on AWS
