If you upload files with the -N flag to > 1 and the file is small enough that this will require a local cache file to be used (due to minimum multipart part size), in some cases it appears that iRODS is doing the writing with only one thread despite the -N flag setting.
Because of this, the S3 plugin is waiting for other threads to write/close before flushing to S3. Instead iRODS is calling the stat operation after the first file closes. This stat is failing because the file has not yet been flushed to S3.
If you upload files with the -N flag to > 1 and the file is small enough that this will require a local cache file to be used (due to minimum multipart part size), in some cases it appears that iRODS is doing the writing with only one thread despite the -N flag setting.
Because of this, the S3 plugin is waiting for other threads to write/close before flushing to S3. Instead iRODS is calling the stat operation after the first file closes. This stat is failing because the file has not yet been flushed to S3.
This seems to be a change between 4.2 and 4.3.