diff options
| author | Zuul <zuul@review.openstack.org> | 2018-02-10 11:24:31 +0000 |
|---|---|---|
| committer | Gerrit Code Review <review@openstack.org> | 2018-02-10 11:24:31 +0000 |
| commit | a4e5190efd9202358b37b363e158ad4bb078d831 (patch) | |
| tree | 6947b354b40a6d91752d822cb91932ba0666d25b | |
| parent | 30b45348cb71922e83dc21e6be261fec6e95fafe (diff) | |
| parent | 6ed7c2bc07e6cede05aa9fc64c2f50f6d302e35b (diff) | |
| download | kolla-a4e5190efd9202358b37b363e158ad4bb078d831.tar.gz kolla-a4e5190efd9202358b37b363e158ad4bb078d831.zip | |
Merge "Replace Chinese single quotes to English single quotes"
| -rw-r--r-- | specs/logging-with-heka.rst | 2 |
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 |