Commit 9edb893c authored by antirez's avatar antirez
Browse files

Crashing is too much in addReplyErrorLength().

See #5663.
parent c55254a5
...@@ -372,12 +372,6 @@ void addReplyErrorLength(client *c, const char *s, size_t len) { ...@@ -372,12 +372,6 @@ void addReplyErrorLength(client *c, const char *s, size_t len) {
serverLog(LL_WARNING,"== CRITICAL == This %s is sending an error " serverLog(LL_WARNING,"== CRITICAL == This %s is sending an error "
"to its %s: '%s' after processing the command " "to its %s: '%s' after processing the command "
"'%s'", from, to, s, cmdname); "'%s'", from, to, s, cmdname);
/* Here we want to panic because when a master is sending an
* error to some slave in the context of replication, this can
* only create some kind of offset or data desynchronization. Better
* to catch it ASAP and crash instead of continuing. */
if (c->flags & CLIENT_SLAVE)
serverPanic("Continuing is unsafe: replication protocol violation.");
} }
} }
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment