summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2014-07-09 16:45:40 +0200
committerantirez <antirez@gmail.com>2014-07-09 16:45:40 +0200
commit067e365042f8d26feff0bf06f8caff1bd9abbbce (patch)
tree16268ac87ad585fa6e3d49d414116aa3a09bb021
parentfda2b303469c35764601bd75516149465f58f786 (diff)
downloadredis-latency.tar.gz
Fixed a few missing newline in createLatencyReport().latency
-rw-r--r--src/latency.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/latency.c b/src/latency.c
index 1ba3a36a5..7dde91a38 100644
--- a/src/latency.c
+++ b/src/latency.c
@@ -209,7 +209,7 @@ sds createLatencyReport(void) {
if (dictSize(server.latency_events) == 0 &&
server.latency_monitor_threshold == 0)
{
- report = sdscat(report,"I'm sorry, Dave, I can't do that. Latency monitoring is disabled in this Redis instance. You may use \"CONFIG SET latency-monitor-threshold <milliseconds>.\" in order to enable it. If we weren't in a deep space mission I'd suggest to take a look at http://redis.io/topics/latency-monitor.");
+ report = sdscat(report,"I'm sorry, Dave, I can't do that. Latency monitoring is disabled in this Redis instance. You may use \"CONFIG SET latency-monitor-threshold <milliseconds>.\" in order to enable it. If we weren't in a deep space mission I'd suggest to take a look at http://redis.io/topics/latency-monitor.\n");
return report;
}
@@ -407,7 +407,7 @@ sds createLatencyReport(void) {
}
if (advise_write_load_info) {
- report = sdscat(report,"- Latency during the AOF atomic rename operation or when the final difference is flushed to the AOF file at the end of the rewrite, sometimes is caused by very high write load, causing the AOF buffer to get very large. If possible try to send less commands to accomplish the same work, or use Lua scripts to group multiple operations into a single EVALSHA call.");
+ report = sdscat(report,"- Latency during the AOF atomic rename operation or when the final difference is flushed to the AOF file at the end of the rewrite, sometimes is caused by very high write load, causing the AOF buffer to get very large. If possible try to send less commands to accomplish the same work, or use Lua scripts to group multiple operations into a single EVALSHA call.\n");
}
if (advise_hz && server.hz < 100) {