You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/09/15 09:02:21 UTC

[jira] [Updated] (SPARK-17534) Increase timeouts for DirectKafkaStreamSuite tests

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

Sean Owen updated SPARK-17534:
------------------------------
    Assignee: Adam Roberts

> Increase timeouts for DirectKafkaStreamSuite tests
> --------------------------------------------------
>
>                 Key: SPARK-17534
>                 URL: https://issues.apache.org/jira/browse/SPARK-17534
>             Project: Spark
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 2.1.0
>            Reporter: Adam Roberts
>            Assignee: Adam Roberts
>            Priority: Trivial
>
> The current tests in DirectKafkaStreamSuite rely on a certain number of messages being received within a given timeframe
> On machines with four+ cores and better clock speeds, this doesn't pose a problem, but on a two core x86 box I regularly see timeouts within two tests within this suite.
> To avoid other users hitting the same problem and needlessly doing their own investigations, let's increase the timeouts. By using 1 sec instead of 0.2 sec batch durations and increasing the timeout to be 100 seconds not 20, we consistently see the tests passing even on less powerful hardware
> I see the problem consistently using a machine with 2x
> Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz and 16 GB of RAM, 1 TB HDD
> Pull request to follow



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org