Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Addresses stuck in configuring when creating large number of queues twice #4765

Open
vbusch opened this issue Jun 18, 2020 · 1 comment
Open
Labels
Milestone

Comments

@vbusch
Copy link
Contributor

vbusch commented Jun 18, 2020

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. create 5000 queues in the standard address space
  2. delete 5000 queues
  3. re-create 5000 queues

Expected behavior
All 5000 queues successfully become active after both creates

Actual behavior
The first 5000 queues become active. Some of the 2nd batch of 5000 queues stay in configuring

Additional context

@lulf lulf changed the title Addresses suck in configuring when creating large number of queues twice Addresses stuck in configuring when creating large number of queues twice Jun 18, 2020
@lulf
Copy link
Member

lulf commented Jun 18, 2020

One of the problems we face in the current scheme, is that we don't have finalizers for addresses, so when an address is deleted, it is not necessarily removed from the router and broker configuration. I think fixing this would require that, which I think we decided to leave for 1.0, which does do that.

@kornys kornys added this to the 1.0.0 milestone Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants