[
https://issues.apache.org/jira/browse/METRON-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658093#comment-15658093
]
ASF GitHub Bot commented on METRON-538:
---------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/344
So,
I can only reproduce this in Travis, and even then it is not every parser
integration test. I have tried a few different things, and have ended up
surprising the KafkaServer log4j logs while creating topics. This seems to
have worked in the build.
On November 10, 2016 at 14:54:07, Otto Fowler ([email protected])
wrote:
Just to clarify, you see this with your local build/test?
On November 10, 2016 at 12:03:46, Otto Fowler ([email protected])
wrote:
I am wondering if it isn’t :
TestUtils.waitUntilMetadataIsPropagated(scala.collection.JavaConversions.asScalaBuffer(servers),
topic, part, 5000);
On November 10, 2016 at 11:46:49, Otto Fowler ([email protected])
wrote:
ERROR KafkaApis:103 - [KafkaApi-0] Error when handling request
> Ensure proper shutdown, exceptions of integration test components
> -----------------------------------------------------------------
>
> Key: METRON-538
> URL: https://issues.apache.org/jira/browse/METRON-538
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.2.2BETA
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Critical
>
> The integration test components use to test with kafka, in mem cluster and
> zookeeper can be left in a failed state, where they are not shut down and
> their resources released. This can lead to cascading failures in the testing
> environment and log pollution.
> The components and their use should be refactored such that they are always
> shut down properly, and log appropriately.
> Some examples will be added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
