diff options
| author | Tobias Henkel <tobias.henkel@bmw.de> | 2018-09-04 13:52:33 +0200 |
|---|---|---|
| committer | Tobias Henkel <tobias.henkel@bmw.de> | 2018-12-11 21:28:59 +0100 |
| commit | fb4c6402a46f8f96ba09f681bfd5356329d416a9 (patch) | |
| tree | 3f4ffa3d614599134a858ece7e750adf9b1b8c99 /requirements.txt | |
| parent | cea6505d1b79ff19ae65a923e4c1c7d00c921604 (diff) | |
| download | zuul-fb4c6402a46f8f96ba09f681bfd5356329d416a9.tar.gz | |
Use gearman client keepalive
If the gearman server vanishes (e.g. due to a VM crash) some clients
like the merger may not notice that it is gone. They just wait forever
for data to be received on an inactive connection. In our case the VM
containing the zuul-scheduler crashed and after the restart of the
scheduler all mergers were waiting for data on the stale connection
which blocked a successful scheduler restart. Using tcp keepalive we
can detect that situation and let broken inactive connections be
killed by the kernel.
Depends-On: I8589cd45450245a25539c051355b38d16ee9f4b9
Change-Id: I30049d59d873d64f3b69c5587c775827e3545854
Diffstat (limited to 'requirements.txt')
| -rw-r--r-- | requirements.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/requirements.txt b/requirements.txt index 4e6611f5e..a7a7779da 100644 --- a/requirements.txt +++ b/requirements.txt @@ -8,7 +8,7 @@ python-daemon>=2.0.4,<2.1.0 extras statsd>=3.0 voluptuous>=0.10.2 -gear>=0.9.0,<1.0.0 +gear>=0.13.0,<1.0.0 apscheduler>=3.0 PrettyTable>=0.6,<0.8 babel>=1.0 |