JIRA - https://issues.apache.org/jira/browse/FALCON-1889 Documentation - https://falcon.apache.org/Operability.html
Falcon creates a topic per feed/process for user notification. ActiveMQ is the usual/default JMS provider used/integrated with Falcon and a topic (with persistent consumer) in ActiveMQ will require a file handle and so for larger number of feed/process combination, this approach is not scalable eclipsed by resource constraints and leaks. The other option is to have one topic but the map message to have feed or process entity name. There is already a FALCON.ENTITY.TOPIC that meets the requirement. With that said, what is the use case and requirements around the user notification with per feed/process JMS topic? I would propose to deprecate it and add any other required info to the FALCON.ENTITY.TOPIC or create a new one topic that satisfies all the needs. Thanks Venky
