3 ms·
Big companies work around this problem by having their own metadata store which is a (non-consistent) replica of S3/GCS' metadata. Netflix built s3mpr to stop
by jamesblonde 10y ago
Big companies work around this problem by having their own metadata store which is a (non-consistent) replica of S3/GCS' metadata.
Netflix built s3mpr to stop problems with Hadoop jobs inserting files, other jobs then starting but not finding the file(s) when they execute a listing for it:
http://techblog.netflix.com/2014/01/s3mper-consistency-in-cloud.html http://techblog.netflix.com/2014/01/s3mper-consistency-in-cl...
Spotify are doing the same for GCS.
AWS have even done it for EMR - http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-fs.html http://docs.aws.amazon.com/ElasticMapReduce/latest/Developer...
- cle 10y agoEven better than a replica, is using a strongly-consistent metadata store to drive the S3 metadata--use the metadata store to acquire unique S3 keys, write to S3, then transact the S3 manifest back to the metadata store. Then you do not have to deal with the problem of replication.