Hi @nafeger,
It looks like “s.s3a.connection.maximum” did not fix the issue this thread too, as we have not implemented that feature. Sorry about the confusion. We are working on these features and will keep you posted
It could be when you tried again it worked. Can you please try the same, re-trying again when there is not much activity on the system?
Thanks,
@balaji.ramaswamy