rajarshisarkar opened a new pull request #3175:
URL: https://github.com/apache/iceberg/pull/3175
Fix for #2991
Seems like for EMR 6.x (Spark 3.x) Iceberg attempts to write the file before
the `tmp` directory is created. This results in `java.io.IOException: No such
file or directory` exception.
The `tmp` files look something like this by default (here
`System.getProperty("java.io.tmpdir")` is
`/mnt1/yarn/usercache/hadoop/appcache/application_1632368478936_0042/container_1632368478936_0042_01_000001/tmp`):
```
/mnt1/yarn/usercache/hadoop/appcache/application_1632368478936_0042/container_1632368478936_0042_01_000001/tmp/s3fileio-2279038237918274355.tmp
/mnt1/yarn/usercache/hadoop/appcache/application_1632368478936_0042/container_1632368478936_0042_01_000001/tmp/s3fileio-2279038237918274355.tmp
/mnt1/yarn/usercache/hadoop/appcache/application_1632368478936_0042/container_1632368478936_0042_01_000001/tmp/s3fileio-2279038237918274355.tmp
```
(or) something like this if `s3fileIoStagingDirectory` is set via
`s3.staging-dir` (`/mnt/tmp` for this case):
```
/mnt/tmp/s3fileio-6715538145691725671.tmp
/mnt/tmp/s3fileio-5266666342669697861.tmp
/mnt/tmp/s3fileio-4592572815837116260.tmp
```
Adding a defensive check to ensure we check the existence of the staging
directory before writing the temp files. With this check I could see the
executor tasks succeeding in `cluster` deploy mode consistently.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
