twitter-archive/kestrel

RELOAD should respond differently if the config failed to reload

Closed this issue · 1 comments

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.