Valery Piashchynski

> @rustatian But it causes downtime. Hundreds of http requests in my case might be lost. You can use green-blue or canary deployments and the moment to switch w/o downtime.

I'm not very familiar with the `nginx`, but as I mentioned, you may try to use green-blue or canary deployment strategies.

Also, take into account, that RR1 was deprecated and will not receive future updates.

Also, I'm not sure, that this feature should be resolved on the server side but not on the DevOps.

Hey @gemini133. The command above resets workers (replace old workers with the new). This operation doesn't cause downtime. However, this reloads only workers, but not the configuration (`.rr.yaml`).

> it'll re-resolve the symlink though? No, configuration by the symlink won't be re-resolved. So, if you change the worker code by the path specified in the configuration it'll be...

Thanks for the FR @OO00O0O. Will be planned after `v2.5.0` release. 👍🏻

I have a few concerns about implementing this feature, because after getting the feedback, some people said, that `M` can be interpreted like (Mebibyte (1048576 bytes) or MegaBytes (100000 bytes))...

You are very welcome. Let's wait for more feedback on this, might be just specifying comments on such fields will be sufficient 😃

@vsychov Thanks for the proposal. We talked with @wolfy-j and decided to investigate the possibility to integrate ha-proxy protocol support into RR :) Stay tuned :+1: