mirror of
https://github.com/fluencelabs/redis
synced 2025-03-17 16:10:50 +00:00
"Timeout receiving bulk data" error message modified.
The new message now contains an hint about modifying the repl-timeout configuration directive if the problem persists. This should normally not be needed, because while the master generates the RDB file it makes sure to send newlines to the replication channel to prevent timeouts. However there are times when masters running on very slow systems can completely stop for seconds during the RDB saving process. In such a case enlarging the timeout value can fix the problem. See issue #695 for an example of this problem in an EC2 deployment.
This commit is contained in:
parent
9a914a632d
commit
f0b9f80345
@ -721,7 +721,7 @@ void replicationCron(void) {
|
||||
if (server.masterhost && server.repl_state == REDIS_REPL_TRANSFER &&
|
||||
(time(NULL)-server.repl_transfer_lastio) > server.repl_timeout)
|
||||
{
|
||||
redisLog(REDIS_WARNING,"Timeout receiving bulk data from MASTER...");
|
||||
redisLog(REDIS_WARNING,"Timeout receiving bulk data from MASTER... If the problem persists try to set the 'repl-timeout' parameter in redis.conf to a larger value.");
|
||||
replicationAbortSyncTransfer();
|
||||
}
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user