diff options
| author | Remi Collet <remi@remirepo.net> | 2020-05-28 12:10:23 +0200 |
|---|---|---|
| committer | Remi Collet <remi@remirepo.net> | 2020-05-28 12:10:23 +0200 |
| commit | d0ecd1252c3703bcdcae4453f648c935b62ed957 (patch) | |
| tree | bce8d6732ee750556a1fb8a3c12b722ec8bbd681 /redis-limit-systemd | |
| parent | 78663de340930276db5a407459d30c62a26e5b96 (diff) | |
add comment for TimeoutStartSec and TimeoutStopSec in limit.conf
fix missing notification to systemd for sentinel
patch from https://github.com/antirez/redis/pull/7168
Diffstat (limited to 'redis-limit-systemd')
| -rw-r--r-- | redis-limit-systemd | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/redis-limit-systemd b/redis-limit-systemd index 8003c2f..a792937 100644 --- a/redis-limit-systemd +++ b/redis-limit-systemd @@ -1,7 +1,14 @@ # If you need to change max open file limit # for example, when you change maxclient in configuration -# you can change the LimitNOFILE value below -# see "man systemd.exec" for information +# you can change the LimitNOFILE value below. +# See "man systemd.exec" for more information. + +# Slave nodes on large system may take lot of time to start. +# You may need to uncomment TimeoutStartSec and TimeoutStopSec +# directives below and raise their value. +# See "man systemd.service" for more information. [Service] LimitNOFILE=10240 +#TimeoutStartSec=90s +#TimeoutStopSec=90s |