falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ying Zheng <yzh...@hortonworks.com>
Subject Re: [DISCUSS] FALCON-1889 JMS user notification creates a topic per feed/process
Date Tue, 19 Apr 2016 22:54:17 GMT
Agree with Venky that creating one topic per entity is not scalable as the
total number of entities can grow large.
One suggestion: ActiveMQ provides JMS message selectors, so the user can
receive only messages whose headers and properties match the selector. If
we add entity name and tag in the message property, the user can use it to
filter the message based on name or tags with one consistent topic.


On 4/19/16, 3:37 PM, "Venkat Ramachandran" <me.venkatr@gmail.com> wrote:

>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
>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.

View raw message