Made spacing after period consistent throughout, removed a couple of spurious commas
This commit is contained in:
		| @@ -15,7 +15,7 @@ The public API is also exposed through the Proxy Server. | ||||
|  | ||||
| A large number of failures are also handled in the Proxy Server. For | ||||
| example, if a server is unavailable for an object PUT, it will ask the | ||||
| ring for a handoff server, and route there instead. | ||||
| ring for a handoff server and route there instead. | ||||
|  | ||||
| When objects are streamed to or from an object server, they are streamed | ||||
| directly through the proxy server to of from the user -- the proxy server | ||||
| @@ -25,7 +25,7 @@ does not spool them. | ||||
| The Ring | ||||
| -------- | ||||
|  | ||||
| A ring represents a mapping between the names of entities stored on disk, and | ||||
| A ring represents a mapping between the names of entities stored on disk and | ||||
| their physical location. There are separate rings for accounts, containers, and | ||||
| objects. When other components need to perform any operation on an object, | ||||
| container, or account, they need to interact with the appropriate ring to | ||||
| @@ -42,13 +42,13 @@ of a partition is guaranteed to reside in a different zone. A zone could | ||||
| represent a drive, a server, a cabinet, a switch, or even a datacenter. | ||||
|  | ||||
| The partitions of the ring are equally divided among all the devices in the | ||||
| Swift installation.  When an event occurs that requires partitions to be | ||||
| moved around (for example if a device is added to the cluster), the ring | ||||
| ensures that a minimum number of partitions are moved at a time, and only | ||||
| one replica of a partition is moved at a time. | ||||
| Swift installation. When partitions need to be moved around (for example if a | ||||
| device is added to the cluster), the ring ensures that a minimum number of | ||||
| partitions are moved at a time, and only one replica of a partition is moved at | ||||
| a time. | ||||
|  | ||||
| Weights can be used to balance the distribution of partitions on drives | ||||
| across the cluster.  This can be useful, for example, if different sized | ||||
| across the cluster. This can be useful, for example, when different sized | ||||
| drives are used in a cluster. | ||||
|  | ||||
| The ring is used by the Proxy server and several background processes | ||||
| @@ -62,7 +62,7 @@ The Object Server is a very simple blob storage server that can store, | ||||
| retrieve and delete objects stored on local devices. Objects are stored | ||||
| as binary files on the filesystem with metadata stored in the file's | ||||
| extended attributes (xattrs). This requires that the underlying filesystem | ||||
| choice for object servers must support xattrs on files. Some filesystems, | ||||
| choice for object servers support xattrs on files. Some filesystems, | ||||
| like ext3, have xattrs turned off by default. | ||||
|  | ||||
| Each object is stored using a path derived from the object name's hash and | ||||
| @@ -95,7 +95,7 @@ Replication | ||||
| ----------- | ||||
|  | ||||
| Replication is designed to keep the system in a consistent state in the face | ||||
| of temporary error conditions like network partitions or drive failures. | ||||
| of temporary error conditions like network outages or drive failures. | ||||
|  | ||||
| The replication processes compare local data with each remote copy to ensure | ||||
| they all contain the latest version. Object replication uses a hash list to | ||||
|   | ||||
		Reference in New Issue
	
	Block a user
	 Brian K. Jones
					Brian K. Jones