Is it possible that the current design of fs.s3fs can lead to fd leaks?
Currently the s3 connections are mane on demand via two properties:
In a use-case of a long-running process utilzing fs as an abstracted file system over S3; this can probably lead to fd/socket leaks. At least in my initial testing it leaves the underlying socket in a CLOSE_WAIT state and doesn't seem tto be garbage collected and cleaned up.
Can anyone confirm this behaviour?
Is it possible that the current design of
fs.s3fscan lead to fd leaks?Currently the s3 connections are mane on demand via two properties:
_s3conn_s3buktIn a use-case of a long-running process utilzing
fsas an abstracted file system over S3; this can probably lead to fd/socket leaks. At least in my initial testing it leaves the underlying socket in aCLOSE_WAITstate and doesn't seem tto be garbage collected and cleaned up.Can anyone confirm this behaviour?