Reload server endpoints on SIGHUP #168

New issue

Open

opened 2024-11-21 12:13:33 +00:00 by potyarkin · 0 comments

potyarkin commented

2024-11-21 12:13:33 +00:00

Member

Currently frostfs-http-gw does not support changing listener endpoints without a restart:

Modify server.address in gateway config
Send SIGHUP to frostfs-http-gw process
New endpoint bindings are not loaded, a warning is printed to logs: failed to reload server parameters {"error": "invalid servers configuration: no known server found"}

Docs clearly mark this scenario as unsupported, but that was not the "least surprising" behavior for me as a user.

Let's discuss whether adding this feature is worth it. If we decide to add it, frostfs-s3-gw should be modified in a similar fashion.

Currently frostfs-http-gw does not support changing listener endpoints without a restart: - Modify `server.address` in gateway config - Send SIGHUP to frostfs-http-gw process - New endpoint bindings are not loaded, a warning is printed to logs: `failed to reload server parameters {"error": "invalid servers configuration: no known server found"}` [Docs](https://git.frostfs.info/TrueCloudLab/frostfs-http-gw/src/branch/master/docs/gate-configuration.md#server-section) clearly mark this scenario as unsupported, but that was not the "least surprising" behavior for me as a user. Let's discuss whether adding this feature is worth it. If we decide to add it, [frostfs-s3-gw](https://git.frostfs.info/TrueCloudLab/frostfs-s3-gw/src/branch/master/docs/configuration.md#server-section) should be modified in a similar fashion.