Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AMQP output with max_messages > 0 keeps opening new connections #4921

Closed
lassizci opened this issue Oct 25, 2018 · 0 comments
Closed

AMQP output with max_messages > 0 keeps opening new connections #4921

lassizci opened this issue Oct 25, 2018 · 0 comments
Labels
area/rabbitmq bug unexpected problem or unintended behavior
Milestone

Comments

@lassizci
Copy link

lassizci commented Oct 25, 2018

Relevant telegraf.conf:

[[outputs.amqp]]
brokers = [ "amqps://rabbit1:5671/", "amqps://rabbit2:5671/", "amqps://rabbit3:5671/",]
username = "foo"
password = "bar"
max_messages = 100
exchange = "telegraf"
delivery_mode = "persistent"
tls_ca = "/etc/telegraf/ssl/ca-chain.crt"
tls_key = "/etc/telegraf/ssl/telegraf-client.key"
tls_cert = "/etc/telegraf/ssl/telegraf-client.crt"

System info:

Ubuntu 16.04.5 LTS
Telegraf 1.8.2 (git: HEAD 996a91f2)

Repro steps

  1. setup 1+ rabbitmq instances
  2. configure telegraf to publish to rabbitmq
  3. set max_messages (perhaps to a low value) and wait

Expected behavior:

Whenever a new connection is established due to reaching max_messages, the old connections should be closed.

Actual behavior:

Connection amount seems to increase indefinitely, which consumes memory and sockets.

@glinton glinton added the bug unexpected problem or unintended behavior label Oct 25, 2018
@danielnelson danielnelson added this to the 1.8.3 milestone Oct 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rabbitmq bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants