Skip to content

Conversation

@michaelklishin
Copy link
Member

@michaelklishin michaelklishin commented Apr 20, 2025

This is a more or less direct port of how the Java client implements topology recovery, sans a few features that can be introduced at a later point:

  • Recovery-time entity filtering
  • Retries

So the scope of this change is strictly #704 and one additional layer of testing (that of Bunny::TopologyRegistry).

Closes #704.

@michaelklishin michaelklishin added this to the 3.0.0 milestone Apr 20, 2025
1. Correct TopologyRegistry
2. Only perform topology recovery after the connection
   and its channels are recovered
3. More logging in recovery tests, less in
   Bunny::Session when connection recovery is
   enabled
@michaelklishin michaelklishin marked this pull request as ready for review April 20, 2025 22:57
@michaelklishin michaelklishin merged commit 3c21c8a into main Apr 21, 2025
3 checks passed
@michaelklishin michaelklishin deleted the bunny-704 branch April 21, 2025 01:51
michaelklishin added a commit that referenced this pull request Dec 31, 2025
Move topology recovery to Bunny::Session
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Scope queue/exchange/binding/consumer tracking [used by connection recovery] per connection (Bunny::Session)

2 participants