Apache/druid
1
0
Fork 0
mirror of https://github.com/apache/druid.git synced 2025-02-17 15:35:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2666 from dclim/caching-doc-fix

Browse Source 
caching doc fix
This commit is contained in:
Fangjin Yang 2016-03-15 18:07:38 -07:00
commit 8c481e496b
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/content/querying/caching.md
View File

@ -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 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, 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 ## Query caching on Historicals
Larger production clusters should enable caching only on the Historicals to avoid having to use Brokers to merge all query 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 results. Enabling caching on the Historicals instead of the Brokers enables the Historicals to do their own local result
on the Brokers. merging and puts less strain on the Brokers.