aboutsummaryrefslogtreecommitdiff
path: root/specs
diff options
context:
space:
mode:
authorgaofei <gao.fei@inspur.com>2018-01-23 16:31:43 +0800
committergaofei <gao.fei@inspur.com>2018-01-23 16:31:43 +0800
commitb51294dc3df5260857d260fdc3c56c85ac8c6766 (patch)
tree52ac52c6c627e3fabdb0939d318dfd7991c56d15 /specs
parent3b6bf187b48a4a182c6da8ac397726636f8fb565 (diff)
downloadkolla-ansible-b51294dc3df5260857d260fdc3c56c85ac8c6766.tar.gz
kolla-ansible-b51294dc3df5260857d260fdc3c56c85ac8c6766.zip
Replace Chinese punctuation with English punctuation
Change-Id: Icc4a984e8defe4d068e7f4a78cd5483a0cb9c7b7
Diffstat (limited to 'specs')
-rw-r--r--specs/logging-with-heka.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/specs/logging-with-heka.rst b/specs/logging-with-heka.rst
index 17ba4b3eb..7cd7770b3 100644
--- a/specs/logging-with-heka.rst
+++ b/specs/logging-with-heka.rst
@@ -62,7 +62,7 @@ run it on every node of the cluster. In contrast, Logstash runs in a JVM and
is known [3] to be too heavy to run on every node.
Another important aspect is flow control and avoiding the loss of log messages
-in case of overload. Heka’s filter and output plugins, and the Elasticsearch
+in case of overload. Heka's filter and output plugins, and the Elasticsearch
output plugin in particular, support the use of a disk based message queue.
This message queue allows plugins to reprocess messages from the queue when
downstream servers (Elasticsearch) are down or cannot keep up with the data