jeantil opened a new pull request, #2423:
URL: https://github.com/apache/james-project/pull/2423
As discussed in the issue, filter topics need to use unique subscription
names to fetch all applicable filters upon restart.
At the moment we use durable subscriptions which means that these
subscriptions accumulate across restarts on the pulsar side, eventually
reaching the limit of allowed subscriptions per topic.
Alternatives
- We could try to be good citizens and delete the subscriptions but there is
no guarantee that the process terminates properly and does the cleanup
- We could use another kind of UUID which is strictly incremental and or
includes a timestamp, allowing to build a safe cleanup script, but it would be
difficult to run automatically in a safe way.
- We could expose the filter subscription names of the active nodes to make
sure the cleanup script doesn't accidentally delete currently used subscriptions
In this PR I propose to use the
[non-durable](https://pulsar.apache.org/docs/3.3.x/concepts-messaging/#what-is-a-subscription-mode)
subscriptions of Pulsar which seem to me to be the safest and cleanest
solution to this issue,
--
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.
To unsubscribe, e-mail: notifications-unsubscr...@james.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@james.apache.org
For additional commands, e-mail: notifications-h...@james.apache.org
