[
https://issues.apache.org/jira/browse/HDDS-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766785#comment-17766785
]
Sumit Agrawal commented on HDDS-9320:
-------------------------------------
As after upgrade ozone, default filesytem is changed to FSO, and delete key
failed is comming as error.
Previously with filesystem with OBS, its comming as Warn, as there was a check
if file exist or not. If not exist, just log warn.
For FSO, exception check is requried for KEY_NOT_FOUND and have warn log, as
file is not present, and having error log is of no meaning in this case.
Warn will represent the operation is perform but file does not exist, the
operation could be avoided.
> Ozone delete key with error log during Spark job completion
> -----------------------------------------------------------
>
> Key: HDDS-9320
> URL: https://issues.apache.org/jira/browse/HDDS-9320
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Sumit Agrawal
> Priority: Minor
>
> Spark Job is trying to cleanup staging directories post successful completion
> of the job but the Ozone BasicOzoneClientAdapterImpl throws an error saying
> "Unable to get File Status".
> {code:java}
> ERROR ozone.BasicOzoneClientAdapterImpl: delete key failed
> Unable to get file status: volume: ozonestage bucket: sparktest key:
> tmp/tpcds_output/q20.out/.spark-staging-836b5b33-3941-4734-8f90-23abdfee9167
> {code}
> _Seen with both Spark2 and Spark3._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
