![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Yoga Ramalingam <yramalingam1@bloomberg.net> | |
| Fri, 31 Oct 2014 20:03:31 +0000 (16:03 -0400) | ||
| committer | Marc Fournier <marc.fournier@camptocamp.com> | |
| Wed, 11 Mar 2015 21:09:42 +0000 (22:09 +0100) | ||
| commit | 5acbb982f1c16b1abb0f088698d7165327718fd4 | |
| tree | 2de22c2814d58d6cf4c2e5d2442021ae0534063b | tree | snapshot |
| parent | d80e639b0ac36e3aa87382c6da93ddc8c4b34170 | commit | diff |
AMQP connection failure leads collectd to use 100%CPU
Summary:
Issue : https://ipm.bloomberg.com/jira/browse/SS-103
Solution : When amqp connection fails, it retries for every message, added a fix to retry only after a delay. A new configuration "ConnectionRetryDelay" has been introduced with default value as 60 seconds.
Test Plan:
1. Tested without the new configuration
2. Tested with the new configuration
In both the cases, verified connection is retried only after the delay and made sure collectd is not taking 100% cpu.
Reviewers: skhajamo
Reviewed By: skhajamo
CC: arcyd
Differential Revision: https://all.phab.dev.bloomberg.com/D149956
Conflicts:
src/amqp.c
Summary:
Issue : https://ipm.bloomberg.com/jira/browse/SS-103
Solution : When amqp connection fails, it retries for every message, added a fix to retry only after a delay. A new configuration "ConnectionRetryDelay" has been introduced with default value as 60 seconds.
Test Plan:
1. Tested without the new configuration
2. Tested with the new configuration
In both the cases, verified connection is retried only after the delay and made sure collectd is not taking 100% cpu.
Reviewers: skhajamo
Reviewed By: skhajamo
CC: arcyd
Differential Revision: https://all.phab.dev.bloomberg.com/D149956
Conflicts:
src/amqp.c
| src/amqp.c | diff | blob | history |