You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering a problem with Orca in my Spinnaker deployment related to queue depth. I've noticed significant delays in task processing, due to a backlog of tasks accumulating in the Orca queue.
Symptoms:
Tasks taking longer than usual to execute.
Pipeline executions getting stuck or delayed.
#Steps Taken:
Scaled up Orca instances.
Questions:
Has anyone else experienced similar queue depth issues with Orca in Spinnaker?
What strategies or best practices have you found effective in addressing this issue?
Are there specific Orca configuration settings or optimizations that helped alleviate queue depth problems?
Are there any known limitations or common pitfalls to watch out for when dealing with Orca queue depth issues?
The text was updated successfully, but these errors were encountered:
Issue Summary:
I'm encountering a problem with Orca in my Spinnaker deployment related to queue depth. I've noticed significant delays in task processing, due to a backlog of tasks accumulating in the Orca queue.
Symptoms:
Tasks taking longer than usual to execute.
Pipeline executions getting stuck or delayed.
#Steps Taken:
Scaled up Orca instances.
Questions:
Has anyone else experienced similar queue depth issues with Orca in Spinnaker?
What strategies or best practices have you found effective in addressing this issue?
Are there specific Orca configuration settings or optimizations that helped alleviate queue depth problems?
Are there any known limitations or common pitfalls to watch out for when dealing with Orca queue depth issues?
The text was updated successfully, but these errors were encountered: