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
If you kick off a tenanted deployment with the same number of tenants as your task cap, and that deployment has a tenanted child deployment, the parent deployments deadlock because there isn't a spare slot in the task cap to run the child deployments.
We need to exclude waiting parent deployments from the task cap count.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 23, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bugThis issue represents a verified problem we are committed to solving
If you kick off a tenanted deployment with the same number of tenants as your task cap, and that deployment has a tenanted child deployment, the parent deployments deadlock because there isn't a spare slot in the task cap to run the child deployments.
We need to exclude waiting parent deployments from the task cap count.
The text was updated successfully, but these errors were encountered: