Client Throwing fileAlreadyExists error and uploading empty file

[bennydean]

We are running a high data volume ETL process to upload JSON files to ADLS using Java Spring. During a load test, the Azure ADLS client began throwing the following error:

com.azure.storage.file.datalake.models.DataLakeStorageException: Status code 409, "{"error":{"code":"PathAlreadyExists","message":"The specified path already exists.

After looking into this, I noticed that the library is creating an empty file and then throwing that error. I am fairly confident that this error is erroneous because we have two different file naming approaches. Some of our files are named by a unique ID for the given event we are processing. Other files are named with a Java generated GUID. Both naming standards generated this error.

I could not find any other information online to help troubleshoot. I am wondering if this is a known bug or if there is some other known issue that may relate to this. Please let me know what information I can include to help troubleshoot this further because I do recognize I have provided limited information in this report.

[bennydean]

Another thing to mention is that within our application, almost 2 minutes goes by from when the application starts uploading and when it throws the error. This to me indicates some other issue and that this exception is just the result of a bad error log. However, this is not something I can confirm on my own.