diff options
| author | antirez <antirez@gmail.com> | 2014-06-16 10:43:05 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2014-06-16 10:43:05 +0200 |
| commit | 56d26c23801b53458dfe8ac614106a9ab71473f1 (patch) | |
| tree | de331f9825d2f95c2cb69cbea4b4cfe667265733 /redis.conf | |
| parent | aa19fd612b39b0270434f4cd049769680dfc74bc (diff) | |
| download | redis-56d26c23801b53458dfe8ac614106a9ab71473f1.tar.gz | |
Client types generalized.
Because of output buffer limits Redis internals had this idea of type of
clients: normal, pubsub, slave. It is possible to set different output
buffer limits for the three kinds of clients.
However all the macros and API were named after output buffer limit
classes, while the idea of a client type is a generic one that can be
reused.
This commit does two things:
1) Rename the API and defines with more general names.
2) Change the class of clients executing the MONITOR command from "slave"
to "normal".
"2" is a good idea because you want to have very special settings for
slaves, that are not a good idea for MONITOR clients that are instead
normal clients even if they are conceptually slave-alike (since it is a
push protocol).
The backward-compatibility breakage resulting from "2" is considered to
be minimal to care, since MONITOR is a debugging command, and because
anyway this change is not going to break the format or the behavior, but
just when a connection is closed on big output buffer issues.
Diffstat (limited to 'redis.conf')
| -rw-r--r-- | redis.conf | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/redis.conf b/redis.conf index fe259726e..1103d6152 100644 --- a/redis.conf +++ b/redis.conf @@ -768,8 +768,8 @@ activerehashing yes # # The limit can be set differently for the three different classes of clients: # -# normal -> normal clients -# slave -> slave clients and MONITOR clients +# normal -> normal clients including MONITOR clients +# slave -> slave clients # pubsub -> clients subscribed to at least one pubsub channel or pattern # # The syntax of every client-output-buffer-limit directive is the following: |