From 9e9c363361bb3d8aaef977efaabea9f0ba52dbe3 Mon Sep 17 00:00:00 2001 From: Thiago da Silva Date: Wed, 14 Aug 2019 18:00:50 +0200 Subject: [PATCH] fix ec overview doc formatting Change-Id: I3fee824e4fdc21aac21a6bb97f24a82d8ea3577d --- doc/source/overview_erasure_code.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/source/overview_erasure_code.rst b/doc/source/overview_erasure_code.rst index 45756c59de..26cf7aa828 100644 --- a/doc/source/overview_erasure_code.rst +++ b/doc/source/overview_erasure_code.rst @@ -646,16 +646,16 @@ multi-phase conversation, that the other nodes have landed enough for a quorum. The basic flow looks like this: - * The Proxy Server erasure codes and streams the object fragments +#. The Proxy Server erasure codes and streams the object fragments (ec_ndata + ec_nparity) to the storage nodes. - * The storage nodes store objects as EC archives and upon finishing object +#. The storage nodes store objects as EC archives and upon finishing object data/metadata write, send a 1st-phase response to proxy. - * Upon quorum of storage nodes responses, the proxy initiates 2nd-phase by +#. Upon quorum of storage nodes responses, the proxy initiates 2nd-phase by sending commit confirmations to object servers. - * Upon receipt of commit message, object servers rename ``.data`` files to +#. Upon receipt of commit message, object servers rename ``.data`` files to include the ``#d`` substring, indicating successful PUT, and send a final response to the proxy server. - * The proxy waits for `ec_ndata + 1` object servers to respond with a +#. The proxy waits for `ec_ndata + 1` object servers to respond with a success (2xx) status before responding to the client with a successful status.