Hello,
As I can’t test anything using AWS EFS it is hard to comment about it. The requirement about not using NFS/CIFS solution for storage is more a strong suggestion than a hard requirement, in the sense that it can work, it’s just usually slower, less reliable, etc. In your case it worked before apparently.
There is no timeout value that could be changed for that. The issue could be related to IO indeed, it could also be about a lack of memory: a user with a similar issue here fixed it by providing more memory to his container.
I can’t really investigate here, but if you want to use this solution, what I can suggest is:
- enable debug mode to if there is more logging, which could help to understand, also make sure to analyze all log messages, not only this Warning
- check what is the real I/O rate on your EFS disk to understand if there is at least something happening or not at all
Cheers