Mailing-List: contact dev-help@edgent.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@edgent.apache.org
Date: Sun, 10 Dec 2017 22:51:00 +0000 (UTC)
From: "Dale LaBossiere (JIRA)" <jira@apache.org>
To: dev@edgent.incubator.apache.org
Message-ID: <JIRA.13124012.1512928183000.427143.1512946260050@Atlassian.JIRA>
In-Reply-To: <JIRA.13124012.1512928183000@Atlassian.JIRA>
References: <JIRA.13124012.1512928183000@Atlassian.JIRA> <JIRA.13124012.1512928183611@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (EDGENT-441) Adjust Kafka tests to tolerate slow
 consumer startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 10 Dec 2017 22:51:08 -0000


     [ https://issues.apache.org/jira/browse/EDGENT-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dale LaBossiere reassigned EDGENT-441:
--------------------------------------

    Assignee: Dale LaBossiere

> Adjust Kafka tests to tolerate slow consumer startup
> ----------------------------------------------------
>
>                 Key: EDGENT-441
>                 URL: https://issues.apache.org/jira/browse/EDGENT-441
>             Project: Edgent
>          Issue Type: Test
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>
> As part of validating 1.2.0 I ran samples/connectors/kafka.
> Manually running of the kafka tests didn't initially succeed due to consumer startup being very slow (10sec?) this time on my Mac for some reason (running local zookeeper & kafka server).
> Adjust both the test's PUB_DELAY_MSEC (15s) and SEC_TIMEOUT (40s) was required to make them pass.
> I'm pretty sure this has nothing to do with the connector/Edgent (but will check more).
> The tests should be changed so as to tolerate this sort of condition if possible  e.g., instead of using a fixed initial delay for publishing, there should be some "gate" that blocks tuple publishing until the subscriber is connected.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)