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

[🐛 BUG]: Redialer does not resume pipeline after delivery channel was closed by RabbitMQ #2091

Open
1 task done
algirdasci opened this issue Dec 13, 2024 · 0 comments
Open
1 task done
Assignees
Labels
B-bug Bug: bug, exception
Milestone

Comments

@algirdasci
Copy link

No duplicates 🥲.

  • I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?

When RabbitMQ closes delivery channel without connection interruption, Redialer does not restore channel and stops processing messages.

Discussion: here

Version (rr --version)

2024.2.1

How to reproduce the issue?

  1. Start RoadRunner
  2. Stop or pause RabbitMQ container
  3. Wait until timeout is reached
  4. Start or resume RabbitMQ container

RR just says pipeline will be recreated, but it is not recreated and messages are stopped to process.

Relevant log output

2024-10-10T14:03:14+0000        DEBUG   rpc             plugin was started      {"address": "tcp://127.0.0.1:6001", "list of the plugins with RPC methods:": ["lock", "kv", "metrics", "resetter", "informer", "app", "jobs"]}
2024-10-10T14:03:14+0000        DEBUG   amqp            pipeline was started    {"driver": "amqp", "pipeline": "rpc", "start": "2024-10-10T14:03:14+0000", "elapsed": 4}
2024-10-10T14:03:15+0000        DEBUG   server          worker is allocated     {"pid": 84205, "max_execs": 0, "internal_event_name": "EventWorkerConstruct"}
2024-10-10T14:03:44+0000        DEBUG   amqp            delivery channel was closed, leaving the AMQP listener
2024-10-10T14:03:44+0000        DEBUG   amqp            exited from redialer
2024-10-10T14:03:44+0000        DEBUG   amqp            number of listeners     {"listeners": 0}
2024-10-10T14:03:44+0000        ERROR   amqp            amqp connection closed  {"error": "Exception (504) Reason: \"channel/connection is not open\""}
2024-10-10T14:03:44+0000        ERROR   amqp            pipeline connection was closed, redialing       {"error": "Exception (501) Reason: \"read tcp 172.23.0.2:57384->192.168.65.254:5672: i/o timeout\"", "pipeline": "rpc", "driver": "amqp", "start": "2024-10-10T14:03:44+0000"}
2024-10-10T14:04:45+0000        ERROR   amqp            backoff operation failed, pipeline will be recreated    {"error": "amqp_driver_redial: Exception (501) Reason: \"read tcp 172.23.0.2:44474->192.168.65.254:5672: i/o timeout\""}
@algirdasci algirdasci added B-bug Bug: bug, exception F-need-verification labels Dec 13, 2024
@rustatian rustatian added this to the v2024.3.2 milestone Dec 13, 2024
@rustatian rustatian moved this to 🔖 Ready in Jira 😄 Dec 14, 2024
@rustatian rustatian modified the milestones: v2024.3.2, v2025.1.0 Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-bug Bug: bug, exception
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants