Running Solr within Kubernetes at Scale
summary
Bloomberg runs over a thousand Solr clouds and indexes tens of billions of documents and the team ports Solr onto Kubernetes by building a Solr Operator that creates StatefulSet + PersistentVolumeClaims, headless services and a set of per-node Services + Ingress so each Solr replica keeps a stable name, address and disk. The operator supports rolling upgrades with per-node status, is open source, runs with local persistent volumes today, has been exercised at 2 clusters × 20 nodes (40 total), and still needs backup/restore and remote-PV testing.
AI-written summary · about
chapters (10)
- 0:00Introduction and Bloomberg context
- 1:08Managing Solr clouds at scale
- 6:04Physical vs logical topology
- 16:03Kubernetes basics for Solr
- 20:42StatefulSets and persistent volumes
- 25:59Networking Solr nodes in Kubernetes
- 27:07Custom Resource Definitions and operators
- 30:39Solr Cloud Operator overview
- 31:23Future of the Solr Cloud Operator
- 32:50Q&A session
related talks
29mScaling Search Clusters with Apache Solr and Kubernetes
29mDemystifying the Solr Operator
39mOperating OpenSearch at Scale With Kubernetes Operators: Lessons Learned and Community Insights
43mRethinking Autoscaling for Apache Solr using Kubernetes
40mOperating Opensearch - The Kubernetes Way
52mOperating OpenSearch at Scale: Lessons From Managing 10,000+ Clusters Across...
14mKeynote: OpenSearch on Kubernetes at Atlassian
35mOrchestrating Resilient Data: Harnessing the Strength of Kubernetes with Operators