News for hackers. Stuff that matters.
Re:HopsFS: 100x Times Faster Than AWS S3 by tutfbhuf on Saturday November 21, 2020 @05:07PM (#25173100)
High-availability durable filesystem is a difficult problem to solve. It usually starts with NFS, which is a big huge single point of failure. Depending on the nature of the application this might be good enough.

But if it's not, you'll typically want cross-datacenter replication so if one rack goes down you don't lose all your data. So then you're looking at something like Glusterfs/MooseFS/Ceph. But the latencies involved with synchronously replicating to multiple datacenters can really kill your performance. For example, try git cloning a large project onto a Glusterfs mount with >20ms ping between nodes. It's brutal.

Other products try to do asynchronous replication, EdgeFS is one I was looking at recently. This follows the general industry trend, like it or not, of "eventually consistent is consistent enough". Not much better than a cron job + rsync, in my opinion, but for some workloads it's good enough. If there's a partition you'll lose data.

Eventually you just give up and realize that a perfectly synchronized geographically distributed POSIX filesystem is a pipe dream, you bite the bullet and re-write your app against S3 and call it a day.

Re:HopsFS: 100x Times Faster Than AWS S3 by geertj on Saturday November 21, 2020 @06:29PM (#25173526)
> It usually starts with NFS, which is a big huge single point of failure.

NFS is just the protocol. Whether it's a single point of failure depends on the server-side implementation. In Amazon EFS it is not.

(disclaimer: I'm a PM-T on the EFS team)

Re:HopsFS: 100x Times Faster Than AWS S3 by ryanmarsh on Saturday November 21, 2020 @10:29PM (#25174715)
Hi, my use case for EFS Lambda is burts of small writes. Could you add a perf mode that favors bursts of small writes? We did some perf tests and just couldn’t make it fast enough.
Re:HopsFS: 100x Times Faster Than AWS S3 by jamesblonde on Sunday November 22, 2020 @04:36AM (#25176180)
What's a small write in your use case? How many KBs is the write op, and how many ops/sec?

We can store small files on NVMe disks in metadata, so that you can read them with a latency of just a couple of ms, and can scale to 10s of thousands of concurrent reads/writes per second with small files.

https://www.logicalclocks.com/blog/millions-and-millions-of-...

Re:HopsFS: 100x Times Faster Than AWS S3 by tw04 on Sunday November 22, 2020 @12:11AM (#25175098)
https://www.netapp.com/cloud-services/cloud-volumes-service-...

You could try NetApp - it's significantly faster than EFS in my experience.

Re:HopsFS: 100x Times Faster Than AWS S3 by SteveNuts on Sunday November 22, 2020 @01:43AM (#25175497)
This solution is at least 40k per year for just the disk controllers, so be prepared for that.
Re:HopsFS: 100x Times Faster Than AWS S3 by tw04 on Sunday November 22, 2020 @10:38AM (#25178267)
First off we're talking about AWS, not on-premises. Second, if we were talking on-premises, you can get into a NetApp controller for FAR less than $40k a year, but that's not really relevant to OP.

There are two options in AWS: one where you get an entire virtual storage system to yourself but also need to have some NetApp expertise (although less than on-premises). You can find pricing here:

https://cloud.netapp.com/pricing

And one where you just consume the NFS/SMB shares more akin to EFS (pricing at the bottom of the page):

https://cloud.netapp.com/cloud-volumes-service-for-aws

In both instances you can get better pricing than what is on that page by working with a partner, but if you don't want to you can buy directly through AWS and pay a slight premium.

Re:HopsFS: 100x Times Faster Than AWS S3 by scoot on Sunday November 22, 2020 @06:45AM (#25176703)
$100/TB/mo for the cloud version.

https://aws.amazon.com/marketplace/pp/B07MF4GHYW

Depending on the use-case, Veritas InfoScale might be a better option. It can aggregate different tiers of storage, and present a multi-node shared-nothing file-system, with options for replication between AZs, regions, or different cloud providers.

Priced by core not capacity.

https://aws.amazon.com/marketplace/pp/B07CYGD14V

Re:HopsFS: 100x Times Faster Than AWS S3 by geertj on Sunday November 22, 2020 @07:23AM (#25176888)
Hi, feel free to reach out with some details on your use case at gerardu at amazon.
Re:HopsFS: 100x Times Faster Than AWS S3 by the8472 on Saturday November 21, 2020 @05:25PM (#25173214)
> For example, try git cloning a large project onto a Glusterfs mount with >20ms ping between nodes. It's brutal.

That may be true but also is due to applications often having very sequential IO patterns even when they don't need to be.

I hope we'll get some convenience wrappers around io_uring that make batching of many small IO calls in a synchronous manner simple and easy for cases where you don't want to deal with async runtimes. E.g. bulk_statx() or fsync_many() would be prime candidates for batching.

Re:HopsFS: 100x Times Faster Than AWS S3 by fxtentacle on Sunday November 22, 2020 @04:44AM (#25176214)
> write your app against S3 and call it a day.

... and then later you notice that you need a special SLA and Amazon Redshift to guarantee that a read from S3 will return the same value as the last write.

Even S3 is only eventually consistent and especially if a US user uploads images into your US bucket and then you serve the URLs to EU users, you might have loading problems. The correct solution, according to our support contact, is that we wait a second after uploading to S3 to make sure at least the metadata has replicated to the EU before we post the image url. That, or pay for Redshift to tell us how long to wait more precisely.

Because contrary to what everyone expects, S3 requests to US buckets might be served by delayed replicas in other countries if the request comes from outside the US.

Re:HopsFS: 100x Times Faster Than AWS S3 by Galanwe on Sunday November 22, 2020 @05:45AM (#25176453)
> The correct solution, according to our support contact, is that we wait a second after uploading to S3

I'm shocked that you got this answer. This is definitely not how you are supposed to operate.

If you need to ensure the sequantiality of a write followed by a read on S3, the idiomatic way is to enable versioning on your bucket, issue a write, and provide the version ID to whoever need to read after that write.

Not only will that transparently ensure that you will not read deprecated data, but it will even ensure that you actually read the result of that particular write, and not any consecutive write that could have happened in between.

This pattern is very easy to implement for sequential operations in a single function, like:

    version = s3.put_object(...)
    data = s3.get_object(version_id=version, ...)
I agree that when you deal with various processes it can become messy.

In practice it never bothered me too much though. I prefer having explicit synchronization through versions, rather than having a blocking write waiting for all caches to be synchronized.

Also, this should only be necessary if you write to an already existing object. New keys will always trigger a cache invalidation from my understanding.

Re:HopsFS: 100x Times Faster Than AWS S3 by fxtentacle on Sunday November 22, 2020 @10:22AM (#25178092)
Depending on your write throughput, versioning can be quite expensive.

Also, we were already at a throughput where the s3 metadata nodes would sometimes go offline, so I'm not sure putting more work on them would have improved our overall situation.

Re:HopsFS: 100x Times Faster Than AWS S3 by Galanwe on Sunday November 22, 2020 @11:25AM (#25178678)
Interesting, do you have more information on how you did monitors these S3 metadata nodes? Never heard of that.

Why would an unversioned put be less costly than a versioned put? To me it should be pretty much the same. I would almost suspect unversioned puts are hacked around versioned ones.

Out of curiosity what kind of workload did you perform? I have been moving terabytes of files (some very small 1kB files, some huge 150GB files) and never noticed a single blip of change in behavior from S3 (and certainly not anything going "off")

Re:HopsFS: 100x Times Faster Than AWS S3 by fxtentacle on Monday November 23, 2020 @07:39AM (#25186111)
> Interesting, do you have more information on how you did monitors these S3 metadata nodes? Never heard of that.

Pretty simple, we started a bulk import, and then HTTPS requests to amazonaws.com started timing out... Later, support told us to spread out our requests to alleviate the load spike.

What we did was process roughly 50mio 1MB JPEG images from the full-res S3 bucket into an derived-data S3 bucket.

Re:HopsFS: 100x Times Faster Than AWS S3 by dividuum on Sunday November 22, 2020 @06:03AM (#25176537)
> S3 requests to US buckets might be served by delayed replicas in other countries if the request comes from outside the US

What? That makes no sense. Do you have a source for that? I thought the explicit choice of region when creating a bucket limits where data is located. Why would the give you geo-replication for free? Also: "Amazon S3 creates buckets in a Region you specify. To optimize latency, minimize costs, or address regulatory requirements, choose any AWS Region that is geographically close to you." - https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket....

Also the consistency when creating objects is described here: https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.... For new objects, you get read-after-write consistency and the example you gave contradicts that.

Re:HopsFS: 100x Times Faster Than AWS S3 by Dunedan on Sunday November 22, 2020 @07:45AM (#25177008)
> For new objects, you get read-after-write consistency and the example you gave contradicts that.

Mind the documented caveat for this case:

> The caveat is that if you make a HEAD or GET request to a key name before the object is created, then create the object shortly after that, a subsequent GET might not return the object due to eventual consistency.

Re:HopsFS: 100x Times Faster Than AWS S3 by dividuum on Sunday November 22, 2020 @09:43AM (#25177791)
Indeed, although that seems irrelevant for the mentioned use case. After all, why would the client request an image before it's uploaded. It seems like a straight forward "server side upload->generate url and send it to client->client requests image" flow. It's perfectly covered by the consistency provided.
Re:HopsFS: 100x Times Faster Than AWS S3 by fxtentacle on Sunday November 22, 2020 @10:24AM (#25178127)
That's what we did. Server side upload, link into websocket, client downloads image. It did work 99.99% of all requests.
Re:HopsFS: 100x Times Faster Than AWS S3 by Dunedan on Sunday November 22, 2020 @11:11AM (#25178571)
I'm surprised about the conclusion of the AWS support that this is intended behavior. I'm curious about the specifics of the behavior of S3 in this case. Do you have any more detailed information from the AWS support you could share by any chance? If you don't mind, I'd be also grateful if you could drop some answers to the questions below.

Do you use S3 replication (CRR/SRR)?

Before uploading, do you make any request to the object key? If yes, what kind of request?

For downloading, do you use pre-signed URLs or is the S3 bucket public?

What's the error the 0,01% of users encounter? Is it a NoSuchKey error?

Re:HopsFS: 100x Times Faster Than AWS S3 by fxtentacle on Sunday November 22, 2020 @10:17AM (#25178034)
They also say "A process writes a new object to Amazon S3 and immediately lists keys within its bucket. Until the change is fully propagated, the object might not appear in the list" which implies that you cannot read immediately after write.
Re:HopsFS: 100x Times Faster Than AWS S3 by dividuum on Sunday November 22, 2020 @11:32AM (#25178718)
No. It does not imply that. It only implies that it might not be included in a List Operation. That's all this sentence tells you.
Re:HopsFS: 100x Times Faster Than AWS S3 by slaymaker1907 on Saturday November 21, 2020 @06:30PM (#25173533)
You can minimize the effects of eventual consistency by distinguishing the distant replicas from the same-datacenter ones. Cross datacenter/region might be eventually consistent, but you will only see it rarely since the same-datacenter replicas are fully consistent with each other.

The main downside is that you have to pick one datacenter as the main datacenter at any given time. This can change if the old one goes down or due to business needs, but you can't have two of them as the main datacenter at once for a given dataset.

Re:HopsFS: 100x Times Faster Than AWS S3 by jmpman on Sunday November 22, 2020 @01:34AM (#25175463)
Know of any commercial offerings with that characteristic?
Re:HopsFS: 100x Times Faster Than AWS S3 by Cixelyn on Saturday November 21, 2020 @07:12PM (#25173718)
> EdgeFS is one I was looking at recently

Do you have any additional info? EdgeFS's github[1] doesn't work; does repo access require a Nexenta sales call?

We're also looking into asynchronously replicated FSs, I think built-in caching + tiering is slightly nicer than cron + rsync; would love to know what other solutions you looked into.

[1] https://github.com/Nexenta/edgefs

Re:HopsFS: 100x Times Faster Than AWS S3 by rsync on Saturday November 21, 2020 @11:08PM (#25174855)
Don't give up too easily on (something like cron+rsync).

Things like cron+rsync fail in boring ways.

Fancy things fail in fascinating ways.

Re:HopsFS: 100x Times Faster Than AWS S3 by objectivefs on Sunday November 22, 2020 @01:54AM (#25175542)
ObjectiveFS takes a different approach to high-availability durable file system by using S3 as the storage backend and building a log structured file system on top. This leverages the durability and scalability of S3 while allowing e.g. git cloning/diffing of a large project (even cross region) to remain fast. To compare we have some small file benchmark results at https://objectivefs.com/howto/performance-amazon-efs-vs-obje... .
Re:HopsFS: 100x Times Faster Than AWS S3 by harshaw on Saturday November 21, 2020 @06:10PM (#25173439)
EFS attempts to solve this problem, although the speed of light between data centers is still a minor challenge.
Re:HopsFS: 100x Times Faster Than AWS S3 by hanikesn on Saturday November 21, 2020 @08:18PM (#25174038)
Quobyte claim to have solved the synchronized distributed POSIX filesystem (mod geographically ).
Re:HopsFS: 100x Times Faster Than AWS S3 by fock on Saturday November 21, 2020 @05:16PM (#25173161)
wait, S3 can do git now? I guess you are right in nearly everything... but starting with git on gluster and then jumping to selling apples as bananas (e.g. S3) doesn't really make an argument.