aboutsummaryrefslogtreecommitdiff
path: root/specs/logging-with-heka.rst
diff options
context:
space:
mode:
authorchengebj5238 <chengebj@inspur.com>2018-02-05 18:04:06 +0800
committerchengebj5238 <chengebj@inspur.com>2018-02-05 18:06:24 +0800
commit6ed7c2bc07e6cede05aa9fc64c2f50f6d302e35b (patch)
treea6d99e07b87c5c000d231c32d3054f5ce5bb6cb2 /specs/logging-with-heka.rst
parentad80bfd0693f61df5bf46a4ba2dbb0a87d3fe6f9 (diff)
downloadkolla-6ed7c2bc07e6cede05aa9fc64c2f50f6d302e35b.tar.gz
kolla-6ed7c2bc07e6cede05aa9fc64c2f50f6d302e35b.zip
Replace Chinese single quotes to English single quotes
Change-Id: Idabd40606b385430ce35925fa6d1558c835065f1
Diffstat (limited to 'specs/logging-with-heka.rst')
-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