[
https://issues.apache.org/jira/browse/SPARK-32519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169850#comment-17169850
]
Gabor Somogyi commented on SPARK-32519:
---------------------------------------
I'm on 3 weeks vacation but had a slight look at it.
This 30 seconds means the timeout is in place:
{code:java}
The code passed to failAfter did not complete within 30 seconds
{code}
Kafka is known to be flaky in general which is the case here as well.
I've seen this issue before so I don't think the change itself caused it.
It may happen that the change itself made this more frequent but I hardly can
believe that this is the root cause.
As a side note timeout is timeout on all platforms but if I understand it well
this happens only on aarch64, right?
cc [~kabhwan]
> test of org.apache.spark.sql.kafka010.KafkaSourceStressSuite failed for
> aarch64
> -------------------------------------------------------------------------------
>
> Key: SPARK-32519
> URL: https://issues.apache.org/jira/browse/SPARK-32519
> Project: Spark
> Issue Type: Test
> Components: Tests
> Affects Versions: 3.0.0
> Reporter: huangtianhua
> Priority: Major
>
> The aarch64 maven job failed after the commit
> https://github.com/apache/spark/commit/813532d10310027fee9e12680792cee2e1c2b7c7
> merged, see the log
> https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-arm/353/testReport/junit/org.apache.spark.sql.kafka010/KafkaSourceStressSuite/stress_test_with_multiple_topics_and_partitions/
> I took test in my aarch64 instance, if I reset the commit
> 813532d10310027fee9e12680792cee2e1c2b7c7 the test is ok.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
