diff options
| author | Piotr Parczewski <piotr@stackhpc.com> | 2023-03-28 14:08:42 +0200 |
|---|---|---|
| committer | Piotr Parczewski <piotr@stackhpc.com> | 2023-03-28 14:09:01 +0200 |
| commit | 2ddf0aeb204d754636ded6ff2be4e2dcfc3ee421 (patch) | |
| tree | 2a50f7abf3278dff7bee8cd1a61e339bf0a2b026 /specs/logging-with-heka.rst | |
| parent | 41c489715fd676384f766547252b9895fc593d91 (diff) | |
| download | kolla-2ddf0aeb204d754636ded6ff2be4e2dcfc3ee421.tar.gz kolla-2ddf0aeb204d754636ded6ff2be4e2dcfc3ee421.zip | |
Replace invisible unicode chars
They're believed to have no special meaning and were put by accident.
TrivialFix
Change-Id: I66ea5711810ed0060cf89192a780bfcc92e79770
Diffstat (limited to 'specs/logging-with-heka.rst')
| -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 8087a6a41..7b863db17 100644 --- a/specs/logging-with-heka.rst +++ b/specs/logging-with-heka.rst @@ -256,7 +256,7 @@ An alternative to this proposal involves using Logstash in a centralized way as done in [1]. Another alternative would be to execute Logstash on each cluster node, as this -spec proposes with Heka. But this would mean running a JVM on each cluster +spec proposes with Heka. But this would mean running a JVM on each cluster node, and using Redis as a centralized queue. Also, as described above, we initially considered relying on services writing |