metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nickwallen <>
Subject [GitHub] incubator-metron pull request #245: METRON-408 Intermittent Failures of Prof...
Date Wed, 07 Sep 2016 16:24:52 GMT
GitHub user nickwallen reopened a pull request:

    METRON-408 Intermittent Failures of Profile Integration Tests

    The profiler configuration was not being updated from Zookeeper correctly in all cases.
 After some period of time the configurations would be updated and the tests would work. 
But if this period of time was greater than 90 seconds, the amount of time the profile integration
tests wait, then the tests would fail.  
    In all cases, messages were being sent through Storm prior to the bolt actually receiving
the profiler configuration, which would cause the `ProfileSplitterBolt` to throw an exception
indicating that the configuration could not be found. This message `Fatal: Unable to find
valid profiler definition` was a symptom of the problem and occurred much more frequently
than the tests actually failed.
    Since this issue was intermittent, I cannot be sure it is completely gone, but I have
been unable to replicate the problem after these changes.  I also am unable to replicate the
`Fatal: Unable to find valid profiler definition` error after this fix.

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

    $ git pull METRON-408

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 #245
commit d496b4b3a169f6224d5ab07927299277e3cc85b2
Author: Nick Allen <>
Date:   2016-09-07T14:40:33Z

    METRON-408 Intermittent Failures of Profile Integration Tests


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 or file a JIRA ticket
with INFRA.

View raw message