We've seen a case where writing to SFTPFileSystem led to unexpected behaviour:
Given a directory ./data with more than one files in it, the steps it took to get this error was simply:
But not all files show up as in the ls output, in fact more often just one single file shows up in that path...
Digging deeper, we found that rename, mkdirs and create operations in SFTPFileSystem are changing the current working directory during it's execution. For example in create there are:
The issue here is SFTPConnectionPool is caching SFTP sessions (in idleConnections), which contains their current working directory. So after these operations, the sessions will be put back to cache with a changed working directory. This accumulates in each call and ends up causing unexpected weird behaviour. Basically this error happens when processing multiple file system objects in one operation, and relative path is being used.
The fix here is to restore the current working directory of the SFTP sessions.