On Tue, 13 Nov 2007, Bryan Henderson wrote:Both, actually, although there isn't necessarily a strong distinction between the 'central server cluster' and client nodes. For example, storage nodes can double as client nodes (as in a cluster doing distributed computation or some such thing). The system is distributed in the sense that there is no central server limiting scalability. Data storage is distributed across a large cluster of storage nodes (bricks or OSDs), and the metadata (namespace) is managed by a smaller cluster of metadata servers, allowing shared access to the filesystem by many many clients. Aggregate I/O throughput and capacity can be scaled more or less independently from metadata throughput (namespace manipulation) by adjusting the number of nodes devoted to each. sage - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| David Miller | Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. |
| Andrew Morton | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 010/196] Chinese: add translation of Codingstyle |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Felix von Leitner | socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0 |
git: | |
