Auto apply config changes & ability to terminate all processes of a specific worker type

[pjc23]

Currently, when I make a change on the concurrency (i.e. dedicated_count) of a certain worker type, I need to restart the gearman manager service before the config change takes effect. It would be nice if gearman manager automatically adjusts the number of child processes for a certain worker type if the corresponding config section was changed.

Another feature that would be great to have is the ability to terminate all children of a specific worker type. When I'm developing and testing a new worker, it's very usual that I'd have to prematurely stop a specific worker upon realizing an error in the code. However, for this to be done, I'd need to restart the gearman manager service. This is not so good even on a test server because all other worker processes would be killed even if they belong to a different worker type.

I'm not familiar with the inner workings of gearman manager so just let me know if they're not possible

[brianlmoon]

It is possible and interesting. It is not a current pain point for me though. It would be nice if when I update a worker file only workers running that worker file were restarted. So, I am going to leave this here for possible later thought.

[localtest]

I have the similar needs that if it can support auto scaling of a certain worker type based on the config file change or other way without effecting the original process?