RabbitMQ transport: reconnect
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Right now, when connection to broker drops, there is no way to reconnect and restore channels functionality. Also, as I see, `chan []byte`s created by `vice.Transport` blocks forever after disconnection.
I can propose pull request (like [here](https://github.com/devimteam/amqp/blob/master/conn/connection.go#L60)), but not at this moment.
What you think?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining vice.Transport and the referenced conn/connection.go example to understand how broker disconnections affect channels. Reproduce the blocked chan []byte behavior and clarify the reconnect lifecycle before changing it. Done means a dropped RabbitMQ connection can reconnect and restore channel functionality without channels blocking forever.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rabbitmq
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100