Autosharding
Status: Complete — reference articles provided
Priority: Must have
Audience: Search platform, SRE
Why it matters
Large interactive search indices need a shard layout that matches query and ingest load. Earlier evaluation showed that an undersized default layout is not production-ready for heavy interactive workloads; a correctly shaped layout is.
Current state
| Layer | Status |
|---|---|
| Platform autosharding | Available |
| Production path | Complete |
| Customer enablement | Articles provided |
Autosharding is accepted as complete for the Serverless production path. Apply it on interactive indices and keep the layout in the cutover runbook.
Reference articles (shared)
- Data stream autosharding on Serverless
- Replicas and load balancing on Serverless
- Replica management on Serverless
- Search tier autoscaling
- Ingest autoscaling
- Serverless stateless architecture
What to do
- Enable autosharding (or the recommended shard configuration) for interactive indices.
- Confirm layout under production-like query and ingest load as part of Central US cutover testing.
- Document shard settings for rebuild / restore (cutover runbook).
Acceptance criteria
- Platform autosharding available
- Accepted as complete for the production path
- Reference articles provided to the customer team
- Layout documented in the cutover runbook
Related
- Autoscaling, reindex, and ingest stability
- Snapshot restore → Point-in-time restore