diff options
| author | antirez <antirez@gmail.com> | 2014-01-10 15:33:42 +0100 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2014-01-13 16:39:40 +0100 |
| commit | 0ca750d94add42009ba1d1b645fa23c9dcf3796d (patch) | |
| tree | 81112af6701dc9535e24f71c34edbe108b2069ba | |
| parent | 1f9580c125e1a332c19a381bf496b4b63ed4dd2b (diff) | |
| download | redis-0ca750d94add42009ba1d1b645fa23c9dcf3796d.tar.gz | |
Sentinel: releaseSentinelRedisInstance() top comment fixed.
The claim about unlinking the instance from the connected hash tables
was the opposite of the reality. Also the current actual behavior is
safer in most cases, so it is better to manually unlink when needed.
| -rw-r--r-- | src/sentinel.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/sentinel.c b/src/sentinel.c index 611c31f35..3d1477c97 100644 --- a/src/sentinel.c +++ b/src/sentinel.c @@ -942,7 +942,7 @@ sentinelRedisInstance *createSentinelRedisInstance(char *name, int flags, char * } /* Release this instance and all its slaves, sentinels, hiredis connections. - * This function also takes care of unlinking the instance from the main + * This function does not take care of unlinking the instance from the main * masters table (if it is a master) or from its master sentinels/slaves table * if it is a slave or sentinel. */ void releaseSentinelRedisInstance(sentinelRedisInstance *ri) { |