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
When DKG instances shutdown as part of compose, there is a race where the first DKG completes, which causes the container the exit, which causes the docker-compose to stop the other container, which can result in other DKG not completing properly by saving the artefacts to disk, see example.
Proposed solution
Docker-compose shouldn't terminate all containers when the first exits with 0, but rather wait for manual "down" command.
Add a hidden "wait for something signal" before exitting the DKG...?
The text was updated successfully, but these errors were encountered:
Sleep for 2 seconds after successful DKG completion to allow other DKGs to complete as well before exitting causing docker-compose to stop all other containers. This fixes shutdown race in compose DKG tests.
category: test
ticket: #1625
Problem to be solved
When DKG instances shutdown as part of compose, there is a race where the first DKG completes, which causes the container the exit, which causes the docker-compose to stop the other container, which can result in other DKG not completing properly by saving the artefacts to disk, see example.
Proposed solution
The text was updated successfully, but these errors were encountered: