Map-Reduce Ready Distributed File System

摘要

A map-reduce compatible distributed file system that consists of successive component layers that each provide the basis on which the next layer is built provides transactional read-write-update semantics with file chunk replication and huge file-create rates. Containers provide the fundamental basis for data replication, relocation, and transactional updates. A container location database allows containers to be found among all file servers, as well as defining precedence among replicas of containers to organize transactional updates of container contents. Volumes facilitate control of data placement, creation of snapshots and mirrors, and retention of a variety of control and policy information. Also addressed is the use of distributed transactions in a map-reduce system; the use of local and distributed snapshots; replication, including techniques for reconciling the divergence of replicated data after a crash; and mirroring.

主权项

1. A map-reduce compatible distributed file system supported by file system objects, said file system objects comprising any of chunked files, key value stores, and directories, said map-reduce compatible distributed file system comprising:
a container location database (CLDB) configured to maintain information about where each of a plurality of containers is located; a plurality of cluster nodes, each cluster node containing one or more storage pools, each storage pool containing zero or more containers; and a plurality of inodes for structuring said file system objects within said containers; wherein said containers are replicated to other cluster nodes with one container designated as master for each replication chain; wherein said information about where each of a plurality of containers is located that is maintained in said CLDB is itself stored as inodes in well known containers; wherein said CLDB inodes are configured to maintain a database that contains at least following information about all of said containers:
nodes that have replicas of a container; andan ordering of a replication chain for each container; wherein updates to a container are sent to a master for said updated container; wherein changes to content of a container are propagated to said replicas of said container by said master; wherein some file system objects are larger than a single container; and wherein some file system objects are spread over a larger number of nodes than a set represented by a replication chain of a single container.