b96f0fa2df
While a child is abandoned, we must limit the start of anothers with the same name. Otherwise - of the child has startup problems - a number of abandoned children with the same name may queue up. This becomes a problem whenever the child destruction depends on an asynchronous service that provides an env session for the children. If the service is unable to keep up with the session requests (both create and close), the queue of abandoned children becomes unbounded. Limiting the child creation rate to one abandoned child per name mitigates this problem. |
||
|---|---|---|
| .. | ||
| app | ||
| drivers | ||
| init | ||
| lib | ||
| server | ||
| test | ||