From 553b67797158a09cc3e3855b8ae2d4ade7449026 Mon Sep 17 00:00:00 2001 From: dclim Date: Tue, 15 Mar 2016 17:09:33 -0600 Subject: [PATCH] caching doc fix --- docs/content/querying/caching.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/content/querying/caching.md b/docs/content/querying/caching.md index 74f7083f489..1d6f60af441 100644 --- a/docs/content/querying/caching.md +++ b/docs/content/querying/caching.md @@ -14,10 +14,10 @@ can be enabled at either the Historical and Broker level (it is not recommended Enabling caching on the broker can yield faster results than if query caches were enabled on Historicals for small clusters. This is the recommended setup for smaller production clusters (< 20 servers). Take note that when caching is enabled on the Broker, -results from Historicals are returned on a per segment basis, and Historicals will be able to do any local result merging. +results from Historicals are returned on a per segment basis, and Historicals will not be able to do any local result merging. ## Query caching on Historicals Larger production clusters should enable caching only on the Historicals to avoid having to use Brokers to merge all query -results. Enabling caching on the Historicals enables the Historicals do their own local result merging, and puts less strain -on the Brokers. +results. Enabling caching on the Historicals instead of the Brokers enables the Historicals to do their own local result +merging and puts less strain on the Brokers.