[
https://issues.apache.org/jira/browse/SPARK-36701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liujinhui updated SPARK-36701:
------------------------------
Description:
Why does maxOffsetsPerTrigger not work when consuming Kafka, the task fails,
and the yarn retries.
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-sql-kafka-0-10_2.11</artifactId>
<version>2.4.5</version>
</dependency>
[https://stackoverflow.com/questions/55476504/restarting-spark-structured-streaming-job-consumes-millions-of-kafka-messages-an]
There is a similar question here
!image-2021-09-09-13-57-21-175.png!
was:
Why does maxOffsetsPerTrigger not work when consuming Kafka, the task fails,
and the yarn retries.
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-sql-kafka-0-10_2.11</artifactId>
<version>2.4.5</version>
</dependency>
[https://stackoverflow.com/questions/55476504/restarting-spark-structured-streaming-job-consumes-millions-of-kafka-messages-an]
There is a similar question here
> Structured streaming maxOffsetsPerTrigger Invalidation
> -------------------------------------------------------
>
> Key: SPARK-36701
> URL: https://issues.apache.org/jira/browse/SPARK-36701
> Project: Spark
> Issue Type: Bug
> Components: Structured Streaming
> Affects Versions: 2.4.5
> Reporter: liujinhui
> Priority: Major
> Attachments: image-2021-09-09-13-57-21-175.png
>
>
> Why does maxOffsetsPerTrigger not work when consuming Kafka, the task fails,
> and the yarn retries.
> <dependency>
> <groupId>org.apache.spark</groupId>
> <artifactId>spark-sql-kafka-0-10_2.11</artifactId>
> <version>2.4.5</version>
> </dependency>
> [https://stackoverflow.com/questions/55476504/restarting-spark-structured-streaming-job-consumes-millions-of-kafka-messages-an]
> There is a similar question here
> !image-2021-09-09-13-57-21-175.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
