Clarify "configurations" in "Region Data Stores and Data Accessors" topic [#130309083]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/42624de4 Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/42624de4 Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/42624de4 Branch: refs/staging/docs-grant1 Commit: 42624de4a7747898da69ff702ea242c0117650cd Parents: e1ffcd1 Author: Dave Barnes <[email protected]> Authored: Wed Sep 21 14:58:33 2016 -0700 Committer: Dave Barnes <[email protected]> Committed: Wed Sep 21 14:58:33 2016 -0700 ---------------------------------------------------------------------- developing/region_options/data_hosts_and_accessors.html.md.erb | 4 ++++ 1 file changed, 4 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/42624de4/developing/region_options/data_hosts_and_accessors.html.md.erb ---------------------------------------------------------------------- diff --git a/developing/region_options/data_hosts_and_accessors.html.md.erb b/developing/region_options/data_hosts_and_accessors.html.md.erb index d57f795..ed167b6 100644 --- a/developing/region_options/data_hosts_and_accessors.html.md.erb +++ b/developing/region_options/data_hosts_and_accessors.html.md.erb @@ -7,4 +7,8 @@ Understand the difference between members that store data for a region and membe <a id="data_hosts_and_accessors__section_0EF33633F97B4C63AC34F523259AD310"></a> In most cases, when you define a data region in a memberâs cache, you also specify whether the member is a data store. Members that store data for a region are referred to as data stores or data hosts. Members that do not store data are referred to as accessor members, or empty members. Any member, store or accessor, that defines a region can access it, put data into it, and receive events from other members. To configure a region so the member is a data accessor, you use configurations that specify no local data storage for the region. Otherwise, the member is a data store for the region. +For server regions, suppress local data storage at region creation by specifying a region shortcut that contains the term +"PROXY" in its name, such as `PARTITION_PROXY` or `REPLICATE_PROXY`. +For client regions, suppress local data storage at region creation by specifying the `PROXY` region +shortcut. Do not use the `CACHING_PROXY` shortcut for this purpose, as it allows local data storage.
