How Autodesk Migrated 2.3 Billion Documents to Amazon OpenSearch Service
This article details how Autodesk re-architected its single-index Elasticsearch 7.1.1 domain on Amazon OpenSearch Service into a multi-domain setup. Facing performance and scaling limits with 2.3 billion documents, Autodesk adopted a four-domain architecture using Migration Assistant and a custom intelligent routing layer. This solution significantly improved query performance, enabled horizontal scalability, and reduced the blast radius in case of domain unavailability. The migration involved sophisticated bin-packing algorithms to evenly distribute 4.3 million projects across 24 new indices.
- →Autodesk's Initial OpenSearch Service Challenges
- →Re-architected Multi-Domain OpenSearch Service Solution
- →Benefits of the New Architecture
- →Migration Strategy and Data Distribution
Notes (4) ›
- Autodesk's Initial OpenSearch Service Challenges
Autodesk's Forma data management component, which supported search across 2.3 billion documents, ran on a single Elasticsearch 7.1.1 domain with one index. This setup led to degraded query performance, vertical scaling limits on Amazon EC2 instance sizes, and horizontal scaling issues due to hot nodes as data grew.
- Re-architected Multi-Domain OpenSearch Service Solution
Autodesk re-architected their search service into four Amazon OpenSearch Service domains (OpenSearch 2.19), each running 24 m7i.4xlarge.search nodes and hosting six indices. A routing layer uses a DynamoDB table with 4.3 million records to map projects to specific domains, ensuring queries hit only relevant shards.
- Benefits of the New Architecture
The multi-domain architecture offers horizontal scalability by allowing the addition of more domains and indices, efficient routing with queries hitting only specific shards, and a reduced blast radius where only 25% of traffic is affected if a domain fails. It also enables independent scaling of each domain and provides a larger aggregate search-thread pool.
- Migration Strategy and Data Distribution
The migration involved categorizing 4.3 million projects by document count and projected growth using historical data. To ensure even data distribution, a stratified bin-packing algorithm was developed, using an interleaved, round-robin approach for different project size categories to avoid imbalance across the 24 new indices.
https://aws.amazon.com/blogs/big-data/how-autodesk-migrated-2-3-billion-documents-to-amazon-opensearch-service-using-migration-assistant-and-intelligent-routing/
Related releases
- Amazon EC2 Marks 20 Years of Cloud Compute Innovation AWS News Blog ·
- GPU-accelerated Apache Spark on Amazon EMR with EC2 G7 instances runs up to 3.7x faster AWS Big Data Blog ·
- AWS Lambda functions now support full IAM resource-based policies AWS What's New ·
- Amazon MSK 3.7 reaches end of life in 7 days endoflife.date ·
- Amazon ECS adds automated agent connectivity detection and repair AWS What's New ·
- AWS Neuron 2.32 Enhances NKI, MXFP8 Training, and Variable-Size Collectives AWS What's New ·