Distributed Locust on AWS ECS not handling worker status updates

[nicklvsa]

Hello all 👋,

I've got a Locust setup that runs on ECS (a service for the master host and a service for the workers, each running on its own ECS task). Something I've noticed is that if one of the worker tasks gets killed or is replaced (by a deployment for example) the master service does not see this change. Instead, the worker count is incremented and the the master seems to think the previous workers are still reachable.

I didn't want to post this as a bug as it could be due to how we have the services configured, but wanted to see if other folks have seen this behavior and if there's anything I need to do in the workers themselves to ensure they shutdown properly (listening to the correct signals and reporting that signal being fired for example).

For some added context, we're using ECS's service discovery for communication between the two services.

Thanks!
Nick.