GitHub user cestella opened a pull request:

    https://github.com/apache/incubator-metron/pull/139

    METRON-190: Make start_parser_topology.sh more adaptable regarding storm 
topology configuration

    Add the ability to specify the message timeout, the max task parallelism, 
the number of ackers, the number of workers. Also allow the user to pass in 
JSON file containing a map of extra storm configs.
    
    I added the following extra options to `start_parser_topology.sh`:
    ```
     -e,--extra_options <JSON_FILE>            Extra options in the form of a
                                               JSON file with a map for
                                               content.
     -mt,--message_timeout <TIMEOUT_IN_SECS>   Message Timeout in Seconds
     -mtp,--max_task_parallelism <MAX_TASK>    Max task parallelism
     -na,--num_ackers <NUM_ACKERS>             Number of Ackers
     -nw,--num_workers <NUM_WORKERS>           Number of Workers
    ```
    
    For instance, if you wanted to set some storm property on
    the config called `topology.ticks.tuple.freq.secs` to 1000 and 
`storm.local.dir` to `/opt/my/path`
    you could create a file called `custom_config.json` containing
    ```
    {
      "topology.ticks.tuple.freq.secs" : 1000,
      "storm.local.dir" : "/opt/my/path"
    }
    ```
    and pass `--extra_options custom_config.json` to `start_parser_topology.sh`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cestella/incubator-metron 
parser_parallelism_expose

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-metron/pull/139.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #139
    
----
commit 33815e0382b54fb6931bae4579223535e7abdc90
Author: cstella <[email protected]>
Date:   2016-05-27T19:18:12Z

    Exposed more storm topology config options.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to