From b1c1386374aabd085a6d2c9659cc8d50bc0b866a Mon Sep 17 00:00:00 2001 From: antirez Date: Sat, 22 Feb 2014 17:34:46 +0100 Subject: [PATCH] Sentinel: IDONTKNOW error removed. This error was conceived for the older version of Sentinel that worked via master redirection and that was not able to get configuration updates from other Sentinels via the Pub/Sub channel of masters or slaves. This reply does not make sense today, every Sentinel should reply with the best information it has currently. The error will make even more sense in the future since the plan is to allow Sentinels to update the configuration of other Sentinels via gossip with a direct chat without the prerequisite that they have at least a monitored instance in common. --- src/sentinel.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/sentinel.c b/src/sentinel.c index 5de6afea..17d56a1d 100644 --- a/src/sentinel.c +++ b/src/sentinel.c @@ -2468,8 +2468,6 @@ void sentinelCommand(redisClient *c) { ri = sentinelGetMasterByName(c->argv[2]->ptr); if (ri == NULL) { addReply(c,shared.nullmultibulk); - } else if (ri->info_refresh == 0) { - addReplySds(c,sdsnew("-IDONTKNOW I have not enough information to reply. Please ask another Sentinel.\r\n")); } else { sentinelAddr *addr = sentinelGetCurrentMasterAddress(ri);