Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
afc7e08a
Commit
afc7e08a
authored
Jul 17, 2018
by
antirez
Browse files
Panic when we are sending an error to our master/slave.
Related to #5135, see discussion there.
parent
e03358c0
Changes
1
Show whitespace changes
Inline
Side-by-side
src/networking.c
View file @
afc7e08a
...
@@ -349,6 +349,11 @@ void addReplyErrorLength(client *c, const char *s, size_t len) {
...
@@ -349,6 +349,11 @@ 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 an instance is sending an
* error to another instance 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. */
serverPanic
(
"Continuing is unsafe: replication protocol violation."
);
}
}
}
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment