Azure || Pre-Scale Indexer to match Storage
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
The min of 2 containers are not enough to handle the load that 10 storage service containers can handle.
What is the new/expected behavior?
Pre-scaling the Indexer service to 10 containers. Note: The values can be fine-tuned once container bench marking is done for Indexer Service
Have you added/updated Unit Tests and Integration Tests?
N/A