Skip to content

ServiceControl leaks connections with RabbitMQ transport #4226

@ramonsmits

Description

@ramonsmits

Describe the bug

Description

When connectivity to the RabbitMQ broker is interrupted like a RabbitMQ cluster to temporarily not being available because there is no connectivity possible or the cluster is in a minority and does not accept messages it will start to leak connections.

Due to connections not being released the broker can reach its connection limit and reject any new connections causing outage of those services.

Expected behavior

No connections should be leaking when connectivity to the broker is restored and resources should be released.

Actual behavior

Connections are not released and require a restart of ServiceControl to release.

Below is for version 5.2.4

Before:
Before connectivity is lost

After:

After connectivity has restored

Versions

  • 5.0.5
  • 5.2.4

Please list the version of the relevant packages or applications in which the bug exists.

Steps to reproduce

  1. Install SC 5.2.4 primary/audit with RabbitMQ
  2. Stop the broker
  3. Wait a couple of minutes (likely passed the 2 minute period to raise a critical error)
  4. Start the broker
  5. Observe the connections being restored
  6. Wait a while (2 minutes max)
  7. Observe slowly more connections being restored

Relevant log output

No response

Additional Information

Workarounds

Restarting ServiceControl will release all connections

Possible solutions

Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions