fix misspelling of 'server'
Change-Id: I61f916d5734708a821c8d51961fc2d222967f6e8
This commit is contained in:
		| @@ -439,7 +439,7 @@ storage nodes fail, such that sufficient unique fragments are not available in | |||||||
| the local region, a global EC cluster will proceed to read fragments from the | the local region, a global EC cluster will proceed to read fragments from the | ||||||
| other region(s). Random reads from the remote region are not guaranteed to | other region(s). Random reads from the remote region are not guaranteed to | ||||||
| return unique fragments; with EC Duplication there is a significantly high | return unique fragments; with EC Duplication there is a significantly high | ||||||
| probability that the proxy sever will encounter a fragment that is a duplicate | probability that the proxy server will encounter a fragment that is a duplicate | ||||||
| of one it has already found in the local region. The proxy server will ignore | of one it has already found in the local region. The proxy server will ignore | ||||||
| these and make additional requests until it accumulates the required set of | these and make additional requests until it accumulates the required set of | ||||||
| unique fragments, potentially searching all the primary and handoff locations | unique fragments, potentially searching all the primary and handoff locations | ||||||
|   | |||||||
| @@ -2794,7 +2794,7 @@ class ECObjectController(BaseObjectController): | |||||||
|             # TODO: PyECLib <= 1.2.0 looks to return the segment info |             # TODO: PyECLib <= 1.2.0 looks to return the segment info | ||||||
|             # different from the input for aligned data efficiency but |             # different from the input for aligned data efficiency but | ||||||
|             # Swift never does. So calculate the fragment length Swift |             # Swift never does. So calculate the fragment length Swift | ||||||
|             # will actually send to object sever by making two different |             # will actually send to object server by making two different | ||||||
|             # get_segment_info calls (until PyECLib fixed). |             # get_segment_info calls (until PyECLib fixed). | ||||||
|             # policy.fragment_size makes the call using segment size, |             # policy.fragment_size makes the call using segment size, | ||||||
|             # and the next call is to get info for the last segment |             # and the next call is to get info for the last segment | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user
	 lvxianguo
					lvxianguo