Fault Tolerant Execution Mode - Azure Storage Issues

(Cross Posted from Slack) Has anyone using Fault Tolerant mode run into Azure Batch Operations errors when deleting the Paths (folders) during the blob cleanup? We are getting a “BatchDeleteBlob;ClientOtherError” error when trying to cleanup the parent paths. After a bit of research it seems that the Batch Operator is conflicting with a “Lock” on the deleted blob. Could be a background process hasn’t released the deleted object? Thanks.

Resolved in slack - issue was created to resolve this

This was resolved by Using ADLS - GEN - 1 Storage. ADLS GEN 2 Hierarchical Storage is not supported. We created an additional Storage Account and added the Fault Tolerant Execution location to it. It is now working as expected. I asked to have the Documentation clearly state that the Storage needs to be Flat or Non-Hierarchical.

1 Like