metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (METRON-1805) Provide a default value for the Storm topology.max.spout.pending setting
Date Wed, 03 Oct 2018 21:53:00 GMT


ASF GitHub Bot commented on METRON-1805:

GitHub user merrimanr opened a pull request:

    METRON-1805: Provide a default value for the Storm topology.max.spout.pending setting

    ## Contributor Comments
    Users have reported problems in the random and batch indexing topologies when this setting
is not set.  The primary purpose of this PR is to start a discussion around providing a default
value for the Storm topology.max.spout.pending setting in our topologies and implement the
changes if we decide to do it.  
    1. Should we provide defaults or continue to defer to the Storm default where a maximum
isn't enforced?
    2. Which topologies should we provide defaults for?
    3. What should the default values be for the topologies we include?
    ## Pull Request Checklist
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](
for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](
for complete smoke testing guides.  
    In order to streamline the review of the contribution we ask you follow these guidelines
and ask you to double check the following:
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at
[Metron Jira](
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are
trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically
    ### For code changes:
    - [ ] Have you included steps to reproduce the behavior or problem that is being changed
or addressed?
    - [ ] Have you included steps or a guide to how the change may be verified and tested
    - [ ] Have you ensured that the full suite of tests and checks have been executed in the
root metron folder via:
      mvn -q clean integration-test install && dev-utilities/build-utils/

    - [ ] Have you written or updated unit tests and or integration tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way
that is compatible for inclusion under [ASF 2.0](
    - [ ] Have you verified the basic functionality of the build by building and running locally
with Vagrant full-dev environment or the equivalent?
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered
by building and verifying the site-book? If not then run the following commands and the verify
changes via `site-book/target/site/index.html`:
      cd site-book
      mvn site
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci]( is set up for your personal
repository such that your branches are built there before submitting a pull request.

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

    $ git pull METRON-1805

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

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

    This closes #1221
commit 6988e0607afc1cd402063e0696a1220cc134d9d1
Author: merrimanr <merrimanr@...>
Date:   2018-10-03T21:45:32Z

    initial commit


> Provide a default value for the Storm topology.max.spout.pending setting
> ------------------------------------------------------------------------
>                 Key: METRON-1805
>                 URL:
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Ryan Merriman
>            Priority: Major
> Should we provide a default value for this property?  Which topologies should that apply

This message was sent by Atlassian JIRA

View raw message