3 ms·

Disclosure: I work on Google Cloud. It wasn't obvious to me if this is somehow mounting EFS over !NFS (since never says the words NFS in the post). My main fea

by boulos 6y ago

Disclosure: I work on Google Cloud. It wasn't obvious to me if this is somehow mounting EFS over !NFS (since never says the words NFS in the post). My main fear when people say "Should I use Lambda / Google Cloud Functions / Cloud Run against my NFS server" my response isn't "How would you set that up" it's "Be careful. Cleaning up NFS locks held by clients that have gone away is fairly painful, and you have none of the mechanisms to make sure it exits properly". Alternatively, you can mount without locking, and then you get one of the comments downthread about "and now you've given functions shared mutable state but with bad primitives". tl;dr: Cool! ... But, how does this handle NFS locking?

geertj 6y ago
(PM-T in the EFS team) This is NFS and locking is fully supported (the blog includes an example). Because EFS implements the NFS 4.0/4.1 protocols, locks are lease-based and there isn't a need to clean them up. In the unlikely event of a client crash where the client still held locks, they will automatically expire once the associated lease expires.