Skip to content

Reduce DG Engine min replicas to 1#4811

Merged
beastoin merged 1 commit intomainfrom
task/reduce-dg-engine-min-replicas-to-1
Feb 15, 2026
Merged

Reduce DG Engine min replicas to 1#4811
beastoin merged 1 commit intomainfrom
task/reduce-dg-engine-min-replicas-to-1

Conversation

@thainguyensunya
Copy link
Copy Markdown
Collaborator

Change:

  • Reduce DG Engine min replicas to 1

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request reduces the minimum number of replicas for the DG Engine from 4 to 1 in the prod_omi_values.yaml configuration. While this change may aim for cost savings, it critically compromises the high availability of the service by creating a single point of failure in a production environment. If the single engine pod fails, the service could experience significant downtime. I have added a critical review comment recommending this value be increased to ensure service resilience.

engine:
# -- Minimum number of Engine replicas.
minReplicas: 4
minReplicas: 1
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

Reducing minReplicas to 1 in a production environment introduces a critical availability risk. With a single replica, the service has no redundancy and becomes a single point of failure. If the pod goes down, the service will be unavailable until a new one starts, which could take a significant amount of time based on your startup probe configuration (over 15 minutes). For production-grade resilience, a minimum of 2 replicas is highly recommended. Please consider reverting to the previous, safer value.

      minReplicas: 4

@beastoin beastoin merged commit b537b6f into main Feb 15, 2026
1 check passed
@beastoin beastoin deleted the task/reduce-dg-engine-min-replicas-to-1 branch February 15, 2026 01:50
ellaaicare pushed a commit to ellaaicare/omi that referenced this pull request Apr 12, 2026
Glucksberg pushed a commit to Glucksberg/omi-local that referenced this pull request Apr 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants