Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 0.6.0
    • Labels:
      None

      Description

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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                justinleet Justin Leet
                Reporter:
                justinleet Justin Leet
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: