Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

Durable consistent hashing exchange cannot recover their previous state after node restart (3.8.4-specific) #45

Closed
michaelklishin opened this issue Jun 12, 2020 · 1 comment · Fixed by #46
Closed

Durable consistent hashing exchange cannot recover their previous state after node restart (3.8.4-specific) #45

michaelklishin opened this issue Jun 12, 2020 · 1 comment · Fixed by #46
Labels
bug
Milestone
3.8.5

Comments

@michaelklishin
Copy link
Member

Filing only for visibility, the actual behavior change is due to later plugin activation, see rabbitmq/rabbitmq-server#2381.
@michaelklishin michaelklishin mentioned this issue Jun 12, 2020
Closed
michaelklishin added a commit that referenced this issue Jun 12, 2020
@michaelklishin
Manually recover ring state from durable exchanges and bindings
9976605 
Only relevant for some use cases post-3.8.4 which has moved
plugin activation to a later point in the boot cycle, after
topology recovery.

Previously this state was naturally recovered during the topology
recovery boot step.

Closes #45.
@michaelklishin michaelklishin mentioned this issue Jun 12, 2020
Merged
michaelklishin added a commit that referenced this issue Jun 12, 2020
@michaelklishin
Integration tests for #45
4a6cf97
@michaelklishin michaelklishin added this to the 3.8.5 milestone Jun 12, 2020
@michaelklishin michaelklishin mentioned this issue Jun 13, 2020
Closed
@michaelklishin
Copy link
Member Author

Worth mentioning that this partially addresses #17. I'm not currently sure what would be a straightforward way to reconcile the needs of #17 and Jump consistent hashing's approach to ring population. But FWIW the ring repopulation now more stable/predictable w.r.t queue positions on the ring after first node restart.

@michaelklishin michaelklishin changed the title Durable consistent hashing exchange cannot recover their previous state after node restart (3.8.4+) Durable consistent hashing exchange cannot recover their previous state after node restart (3.8.4-specific) Jun 15, 2020
@michaelklishin michaelklishin mentioned this issue Oct 15, 2020
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
3.8.5
1 participant
@michaelklishin