[jira] [Resolved] (SPARK-33230) FileOutputWriter jobs have duplicate JobIDs if launched in same second

["Dongjoon Hyun (Jira)" <ji...@apache.org>]

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

Dongjoon Hyun resolved SPARK-33230.
-----------------------------------
    Fix Version/s: 2.4.8
                   3.0.2
                   3.1.0
       Resolution: Fixed

Issue resolved by pull request 30141
[https://github.com/apache/spark/pull/30141]

> FileOutputWriter jobs have duplicate JobIDs if launched in same second
> ----------------------------------------------------------------------
>
>                 Key: SPARK-33230
>                 URL: https://issues.apache.org/jira/browse/SPARK-33230
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.7, 3.0.1
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>             Fix For: 3.1.0, 3.0.2, 2.4.8
>
>
> The Hadoop S3A staging committer has problems with >1 spark sql query being launched simultaneously, as it uses the jobID for its path in the clusterFS to pass the commit information from tasks to job committer. 
> If two queries are launched in the same second, they conflict and the output of job 1 includes that of all job2 files written so far; job 2 will fail with FNFE.
> Proposed:
> job conf to set {{"spark.sql.sources.writeJobUUID"}} to the value of {{WriteJobDescription.uuid}}
> That was the property name which used to serve this purpose; any committers already written which use this property will pick it up without needing any changes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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