You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Genmao Yu (JIRA)" <ji...@apache.org> on 2019/04/03 13:37:00 UTC

[jira] [Created] (SPARK-27355) make query execution more sensitive to epoch message late or lost

Genmao Yu created SPARK-27355:
---------------------------------

             Summary: make query execution more sensitive to epoch message late or lost
                 Key: SPARK-27355
                 URL: https://issues.apache.org/jira/browse/SPARK-27355
             Project: Spark
          Issue Type: Improvement
          Components: Structured Streaming
    Affects Versions: 3.0.0
            Reporter: Genmao Yu


In SPARK-23503, we enforce sequencing of committed epochs for Continuous Execution. In case a message for epoch n is lost and epoch (n + 1) is ready for commit before epoch n is, epoch (n + 1) will wait for epoch n to be committed first. With extreme condition, we will wait for `epochBacklogQueueSize` (10000 in default) epochs and then failed. There is no need to wait for such a long time before query fail, and we can make the condition more sensitive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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