diff options
| author | Quentin Young <qlyoung@nvidia.com> | 2021-08-11 20:11:02 +0200 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2024-12-09 18:35:42 +0100 |
| commit | 5fba3c4d74af2bc4156468e3d96b0f3ad971c993 (patch) | |
| tree | 3285737291cc3a9eb100c66cd14755f2532d9dc1 /watchfrr/watchfrr.c | |
| parent | pbrd: fix vrf_unchanged which may depend on other seqs (diff) | |
| download | frr-5fba3c4d74af2bc4156468e3d96b0f3ad971c993.tar.xz frr-5fba3c4d74af2bc4156468e3d96b0f3ad971c993.zip | |
watchfrr: increase restart timer 20s -> 90s
This commit:
"tools: run `vtysh -b` once for all-startup"
changed things so that `vtysh -b` is run after all daemons have started
up instead of doing it for each daemon as they are started up. This
results in one long `vtysh -b`, which for large configs and many daemons
(in the case I saw, 4 daemons and 30,000 line config) can exceed the 20
second timer watchfrr uses to kill "hung" background tasks.
Shouldn't be any harm to increasing this to 90 seconds to give us some
leeway while still making sure we kill anything truly misbehaving.
Signed-off-by: Quentin Young <qlyoung@nvidia.com>
Diffstat (limited to '')
| -rw-r--r-- | watchfrr/watchfrr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/watchfrr/watchfrr.c b/watchfrr/watchfrr.c index acc612c0a..611a7872d 100644 --- a/watchfrr/watchfrr.c +++ b/watchfrr/watchfrr.c @@ -44,7 +44,7 @@ #define DEFAULT_PERIOD 5 #define DEFAULT_TIMEOUT 90 -#define DEFAULT_RESTART_TIMEOUT 20 +#define DEFAULT_RESTART_TIMEOUT 90 #define DEFAULT_LOGLEVEL LOG_INFO #define DEFAULT_MIN_RESTART 60 #define DEFAULT_MAX_RESTART 600 |