jbertram commented on issue #2850: ARTEMIS-2504 implement retroactive addresses URL: https://github.com/apache/activemq-artemis/pull/2850#issuecomment-536725956 As noted, separating the ring queues onto their own address means better configuration flexibility. This is mainly for `max-size-bytes` and `address-full-policy` because of the way these specific settings can impact ring-queues (see the ring queue docs on paging for more details on that). In short, if your ring-queue for retroactive functionality is on the main address and that address starts paging then the retroactive functionality "breaks" in that newly created queues won't get any of the messages sent after paging started. Address-settings can and do update queues. The `retroactive-message-count` that I implemented is one example of this. You can see other examples of this in `org.apache.activemq.artemis.core.server.impl.QueueImpl.AddressSettingsRepositoryListener`. If there are address-settings which currently don't update queues which should we can implement those a separate PR. I'm not clear on what specifically will be "messy" about configuring address-settings for the separate address. For an address named "myRetroactiveAddress" with a `retroactive-message-count` > 0 users should be able to use a match like `*.myRetroactiveAddress.#.retro` to configure what they need.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
