Juju Gui Redis

Channel Revision Published Runs on
latest/stable 7 19 Mar 2021
Ubuntu 14.04
latest/edge 7 19 Mar 2021
Ubuntu 14.04
juju deploy juju-gui-redis
Show information

Platform:

Ubuntu
14.04

Learn about configurations >

  • databases | int

    Default: 16

    Set the number of databases. The default database is DB 0. You can select a different one on a per-connection basis using SELECT <dbid> where dbid is a number between 0 and 'databases'-1.

  • logfile | string

    Default: /var/log/redis/redis-server.log

    Specify the log file name.

  • loglevel | string

    Default: notice

    Specify the Redis server verbosity level. Choices are: - debug (a lot of information, useful for development/testing); - verbose (many rarely useful info, but not a mess like the debug level); - notice (moderately verbose, what you want in production probably); - warning (only very important / critical messages are logged).

  • maxmemory | string

    Don't use more than the specified amount of memory. When the memory limit is reached Redis will try to remove keys according to the eviction policy selected (see "maxmemory-policy" below). If Redis can't remove keys according to the policy, or if the policy is set to "noeviction", Redis will start to reply with errors to commands that would use more memory, like SET, LPUSH, and so on, and will continue to reply to read-only commands like GET. This option is usually useful when using Redis as an LRU cache, or to set a hard memory limit for an instance (using the "noeviction" policy). It is possible to specify the memory size in the usual form of 1k, 5GB, 4M and so forth: - 1k: 1000 bytes; - 1kb: 1024 bytes; - 1m: 1000000 bytes; - 1mb: 1024*1024 bytes; - 1g: 1000000000 bytes; - 1gb: 1024*1024*1024 bytes.

  • maxmemory-policy | string

    Default: volatile-lru

    how Redis will select what to remove when maxmemory is reached. You can select among five behaviors: - volatile-lru: remove the key with an expire set using an LRU algorithm; - allkeys-lru: remove any key according to the LRU algorithm; - volatile-random: remove a random key with an expire set; - allkeys-random: remove a random key, any key; - volatile-ttl: remove the key with the nearest expire time (minor TTL); - noeviction: don't expire at all, just return an error on write operations. Note: with any of the above policies, Redis will return an error on write operations, when there are no suitable keys for eviction.

  • memory-overcommit | boolean

    Default: True

    Set the Linux kernel overcommit memory setting to 1 so that no memory overcommit handling is performed. When this is enabled, the performance for memory-intensive tasks is increased, but there is more risk of memory overload. This option is ignored when the charm is deployed to a local environment.

  • password | string

    Require clients to issue AUTH <PASSWORD> before processing any other commands.

  • port | int

    Default: 6379

    Accept connections on the specified port.

  • tcp-keepalive | int

    If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence of communication. This is useful to detect dead peers and to take the connection alive from the point of view of network quipment in the middle. The specified value is in seconds.

  • timeout | int

    Close the connection after a client is idle for N seconds (0 to disable).