From f0e46857b718b2232c813d7ef219da1150807853 Mon Sep 17 00:00:00 2001 From: lvxianguo Date: Fri, 22 Jun 2018 18:30:56 +0800 Subject: [PATCH] fix misspelling of 'server' Change-Id: I61f916d5734708a821c8d51961fc2d222967f6e8 --- doc/source/overview_erasure_code.rst | 2 +- swift/proxy/controllers/obj.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/overview_erasure_code.rst b/doc/source/overview_erasure_code.rst index b885409398..45756c59de 100644 --- a/doc/source/overview_erasure_code.rst +++ b/doc/source/overview_erasure_code.rst @@ -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 other region(s). Random reads from the remote region are not guaranteed to 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 these and make additional requests until it accumulates the required set of unique fragments, potentially searching all the primary and handoff locations diff --git a/swift/proxy/controllers/obj.py b/swift/proxy/controllers/obj.py index 11b42179ed..5c6948c242 100644 --- a/swift/proxy/controllers/obj.py +++ b/swift/proxy/controllers/obj.py @@ -2794,7 +2794,7 @@ class ECObjectController(BaseObjectController): # TODO: PyECLib <= 1.2.0 looks to return the segment info # different from the input for aligned data efficiency but # 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). # policy.fragment_size makes the call using segment size, # and the next call is to get info for the last segment