[
https://issues.apache.org/jira/browse/METRON-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546720#comment-16546720
]
ASF GitHub Bot commented on METRON-1657:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/1099
@ottobackwards I agree, our bolts tend to do the same magic set of
incantations to set up stellar. It'd be better to either try to infer that
initialization where possible or to externalize that logic. Agreed that it's
not this PR that should do that, but I would expect that we should probably
consider a separate JIRA to the effect:
* Decouple ParserBolt the parserbolt initialization and execution logic
into a separate component from the Storm Bolt infrastructure (this will aid in
NiFi or spark integration).
Thoughts? If we agree, then I'll create the JIRA.
> Parser aggregation in storm
> ---------------------------
>
> Key: METRON-1657
> URL: https://issues.apache.org/jira/browse/METRON-1657
> Project: Metron
> Issue Type: Bug
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> Currently our parsing solution requires one storm topology per sensor. It has
> been complained that this may be wasteful of resources and that, rather than
> one storm topology per sensor, it would be advantageous to have multiple
> sensors in the same topology. The benefit to this is that it would require
> fewer storm slots.
> The issue with this is that whenever we've aggregated functionality like this
> before, we've run into issues appropriately being able to scale storm (e.g.
> batch vs random access indexing in the same topology). The main point in
> addressing this is to recommend that parsers with similar velocities and
> complexity are grouped together.
> Particularly for a first cut, leave the configuration mostly as-is, while
> allowing for comma separated lists of sensors in start_parser_topology.sh
> (e.g. bro,yaf creates a aggregated parser consisting of those two).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
