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
I deployed my code to pre-production env (default respawn=True) and then I wanted to experiment with respawn=False as the processes get spawned out of control (because the celery children are not getting stopped when the parent bash script dies)
but I wasnt able to just update the config (runs in a kubernetes container) and re-test .. so had to use circusctl , but unfortunately I wasnt able to set respawn=False and test roght away
➜ circusctl set worker-1 respawn True
ok
➜ circusctl get worker-1 respawn
respawn: False
if the setting update needs a config reload or something, at least an err message would be great vs the misleading "ok" as if the update was successful
Same happens for "singleton" as well
well basically, it'll happen for all left out options in watcher.py::set_opt
The text was updated successfully, but these errors were encountered:
https://github.com/circus-tent/circus/blob/master/circus/watcher.py#L1081
set_opt
does not handle bool options like "respawn" , "singleton" , etc.I deployed my code to pre-production env (default
respawn=True
) and then I wanted to experiment withrespawn=False
as the processes get spawned out of control (because the celery children are not getting stopped when the parent bash script dies)but I wasnt able to just update the config (runs in a kubernetes container) and re-test .. so had to use
circusctl
, but unfortunately I wasnt able to setrespawn=False
and test roght awayif the setting update needs a config reload or something, at least an err message would be great vs the misleading "ok" as if the update was successful
Same happens for "singleton" as well
well basically, it'll happen for all left out options in
watcher.py::set_opt
The text was updated successfully, but these errors were encountered: