I think this is a great product, but I've been actively avoiding NFS for a while now. It's a real shame that there isn't a better network FS protocol standardized already - NFS is complex, is usually a single point of failure (would be interesting to know if EFS isn't...) and comes with a whole set of cruft.
Amazon Elastic File System
51–60 of 217 posts
Re: Amazon Elastic File System
#52Nice. Do they have any details on how the resizing works? Is it automatic as I generate more files? Or will I have to explicitly provision more space as I generate the files?
Re: Amazon Elastic File System
#53I think this is a great product, but I've been actively avoiding NFS for a while now. It's a real shame that there isn't a better network FS protocol standardized already - NFS is complex, is usually a single point of failure (would be interesting to know if EFS isn't...) and comes with a whole set of cruft.
9p is a better network filesystem protocol, and it's available on Linux.
Re: Amazon Elastic File System
#54Re: Amazon Elastic File System
#55I think this is a great product, but I've been actively avoiding NFS for a while now. It's a real shame that there isn't a better network FS protocol standardized already - NFS is complex, is usually a single point of failure (would be interesting to know if EFS isn't...) and comes with a whole set of cruft.
9p is a better network filesystem protocol, and it's available on Linux.
Re: Amazon Elastic File System
#56Does anyone else cringe when someone suggestions using NFS in production? I can't be the only one that has been woken up at 2am because of an NFS outage.
Although skeptical about it going into the project, I've deployed a virtualized oracle rac environment over 10G NFS and with some tuning it was stable and performant. If it is good enough for rac, which has some of the most stringent latency / performance requirements that I've seen, I'd say that it is probably good enough for quite a few production use cases, although to be fair this was only an 8 node cluster.
1) I thought the really high end DBs like to manage their own block storage. Your NFS comment suggests that the database data files were running on an NFS mount, and you had a 10 gig Ethernet connection to the file server.
2) What would you say is the average size of a RAC cluster in (your opinion)? Is 8 considered a small cluster in this realm?
3) DBs have stringent requirements when it comes to operations like sync. Can you actually get ACID in an NFS backed DB?
Thanks for satisfying my curiosity :)
Re: Amazon Elastic File System
#57Earlier quoted context omitted.
9p is a better network filesystem protocol, and it's available on Linux.
What's your experience been running it in production? Any gotchas?
I do have some plans to do benchmarks for another use case that's more performance intensive, but it's buried in my backlog right now.
Re: Amazon Elastic File System
#58This is what should have existed instead of EBS all along. I'll never consider this to be as reliable as S3, but if I'm going to have a network filesystem I'd rather be dealing with NFS as my abstraction instead of virtualized network block devices.
May I ask why? My experience with NFS is pretty bad performance wise.
Re: Amazon Elastic File System
#59We have been needing this very thing for hosting a large number of assets across multiple ec2 instances. Hope they roll this out quickly.
For the record, there has never been anything stopping you from spinning up an NFS EC2 that all of your other EC2s can use.
And you have to resize your block devices to store more stuff.
And...
And...
:-)