Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

RELOAD should respond differently if the config failed to reload #112

Closed
copiousfreetime opened this Issue Oct 29, 2012 · 1 comment

Comments

Projects
None yet
1 participant

When using the RELOAD command over Memcache interface, if there is an error in the config and the server fails to reload the config, the memcache protocol still response with 'Reloaded config.'. I think there should be a different response if there was an error on the server. Maybe SERVER_ERROR?

closing as kestrel is deprecated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment