This is an automated email from the ASF dual-hosted git repository.
kmiller pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new 65da520 GEDOE-4919 Make WAN region creation restrictions more
prominent (#1829)
65da520 is described below
commit 65da520e209055bf1e266d7c8acb325e6ed6ba3d
Author: Karen Miller <[email protected]>
AuthorDate: Thu Apr 19 16:02:56 2018 -0700
GEDOE-4919 Make WAN region creation restrictions more prominent (#1829)
* GEDOE-4919 Make WAN region creation restrictions more prominent
* GEODE-4919 Revise wording per review
---
.../setting_up_a_multisite_system.html.md.erb | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git
a/geode-docs/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html.md.erb
b/geode-docs/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html.md.erb
index 338ca94..0954b22 100644
---
a/geode-docs/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html.md.erb
+++
b/geode-docs/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html.md.erb
@@ -160,7 +160,18 @@ The gateway sender configuration for a specific sender
`id` must be identical on
## <a
id="setting_up_a_multisite_system__section_E1DEDD0743D54831AFFBCCDC750F8879"
class="no-quick-link"></a>Create Data Regions for Multi-site Communication
-When you are using a multi-site configuration, you choose which data regions
to share between sites. Because of the high cost of distributing data between
disparate geographical locations, not all changes are passed between sites.
After you define gateway senders, configure regions to use the gateway sender
to distribute region events.
+When using a multi-site configuration, you choose which data regions to share
between sites. Because of the high cost of distributing data between disparate
geographical locations, not all changes are passed between sites.
+
+
+**Note these important restrictions on the regions:**
+
+- Replicated regions cannot use a parallel gateway sender. Use a serial
gateway sender instead.
+
+- In addition to configuring regions with gateway senders to distribute
events, you must configure the same regions in the target clusters to apply the
distributed events. The region name in the receiving cluster must exactly match
the region name in the sending cluster.
+
+- Regions using the same parallel gateway sender ID must be colocated.
+
+After you define gateway senders, configure regions to use the gateway senders
to distribute region events.
- **gfsh Configuration**
@@ -199,15 +210,6 @@ When you are using a multi-site configuration, you choose
which data regions to
**Note:**
When using the Java API, you must configure a parallel gateway sender
*before* you add its id to a region. This ensures that the sender distributes
region events that were persisted before new cache operations take place. If
the gateway sender id does not exist when you add it to a region, you receive
an `IllegalStateException`.
-**Note:**
-Replicated regions cannot use a parallel gateway sender. Use a serial gateway
sender instead.
-
-**Note:**
-In addition to configuring regions with gateway senders to distribute events,
you must configure the same regions in the target clusters to apply the
distributed events. The region name in the receiving cluster must exactly match
the region name in the sending cluster.
-
-**Note:**
-Regions using the same parallel gateway sender ID must be colocated.
-
## <a
id="setting_up_a_multisite_system__section_E3A44F85359046C7ADD12861D261637B"
class="no-quick-link"></a>Configure Gateway Receivers
Always configure a gateway receiver in each <%=vars.product_name%> cluster
that will receive and apply region events from another cluster.
--
To stop receiving notification emails like this one, please contact
[email protected].
