Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 01963200BC0 for ; Tue, 15 Nov 2016 21:49:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 001CB160B05; Tue, 15 Nov 2016 20:49:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 23470160B03 for ; Tue, 15 Nov 2016 21:49:04 +0100 (CET) Received: (qmail 44430 invoked by uid 500); 15 Nov 2016 20:49:04 -0000 Mailing-List: contact commits-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list commits@geode.incubator.apache.org Received: (qmail 44421 invoked by uid 99); 15 Nov 2016 20:49:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2016 20:49:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D9364C7AF3 for ; Tue, 15 Nov 2016 20:49:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.968 X-Spam-Level: X-Spam-Status: No, score=-5.968 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, KAM_LOTSOFHASH=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4U7Wt1YC5jOi for ; Tue, 15 Nov 2016 20:49:02 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 8E2DD5FC7D for ; Tue, 15 Nov 2016 20:49:02 +0000 (UTC) Received: (qmail 38852 invoked by uid 99); 15 Nov 2016 20:48:48 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2016 20:48:48 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 81549E0AF6; Tue, 15 Nov 2016 20:48:48 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: klund@apache.org To: commits@geode.incubator.apache.org Date: Tue, 15 Nov 2016 20:48:49 -0000 Message-Id: <9a00093d3a894d029f30441cf3b35ca2@git.apache.org> In-Reply-To: <5e985eea15f64f24b4f32a8d65571c60@git.apache.org> References: <5e985eea15f64f24b4f32a8d65571c60@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [02/50] [abbrv] incubator-geode git commit: GEODE-2068 Improve documentation on serial/parallel gateway senders archived-at: Tue, 15 Nov 2016 20:49:06 -0000 GEODE-2068 Improve documentation on serial/parallel gateway senders No parallel senders for distributed regions. Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/9092b4d7 Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/9092b4d7 Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/9092b4d7 Branch: refs/heads/feature/GEODE-1930 Commit: 9092b4d79f1ae96fc4d3f677d09946e96b573a5e Parents: e7d5c6a Author: Karen Miller Authored: Thu Nov 3 16:42:25 2016 -0700 Committer: Karen Miller Committed: Tue Nov 8 13:25:59 2016 -0800 ---------------------------------------------------------------------- .../topology_concepts/multisite_overview.html.md.erb | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/9092b4d7/geode-docs/topologies_and_comm/topology_concepts/multisite_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/topologies_and_comm/topology_concepts/multisite_overview.html.md.erb b/geode-docs/topologies_and_comm/topology_concepts/multisite_overview.html.md.erb index 2ad9a38..f250f80 100644 --- a/geode-docs/topologies_and_comm/topology_concepts/multisite_overview.html.md.erb +++ b/geode-docs/topologies_and_comm/topology_concepts/multisite_overview.html.md.erb @@ -57,26 +57,21 @@ Geode provides two types of gateway sender configurations: *serial* gateway send ## Serial Gateway Senders -A *serial gateway sender* distributes region events from a single Geode server in the local cluster to a remote Geode cluster. Although multiple regions can use the same serial gateway for distribution, a serial gateway uses a single logical event queue to dispatch events for all regions that use the gateway sender. +A *serial gateway sender* funnels region events through a single Geode server in the local cluster to a gateway receiver in the remote Geode cluster. Although multiple regions can use the same serial gateway for distribution, a serial gateway uses a single logical event queue to dispatch events for all regions that use the gateway sender. -Because a serial gateway sender distributes all of a region's events from a single member, it provides the most control over ordering region events as they are distributed across the WAN. However, a serial gateway sender provides only a finite amount of throughput for distributing events. As you add more regions and servers to the local cluster, you may need to configure additional serial gateway senders manually and isolate individual regions on specific serial gateway senders to handle the increased distribution traffic. +Because a serial gateway sender has a single distribution point, it provides the most control over ordering region events as they are distributed across the WAN. However, a serial gateway sender provides only a finite amount of throughput, so it may be a performance bottleneck. As you add more regions and servers to the local cluster, you may need to configure additional serial gateway senders manually and isolate individual regions on specific serial gateway senders to handle the increased distribution traffic. ## Parallel Gateway Senders -A *parallel gateway sender* distributes region events simultaneously from each Geode server that hosts the region. For a partitioned region, this means that each server that hosts buckets for the region uses its own logical queue to distribute events for those buckets. As you add new servers to scale the partitioned region, WAN distribution throughput scales automatically with each new instance of the parallel gateway sender. +A *parallel gateway sender* distributes region events from each of the Geode servers that host a partitioned region. For a partitioned region, each server that hosts primary buckets for the region uses its own logical queue to distribute events for those buckets. As you add new servers to scale the partitioned region, WAN distribution throughput scales automatically with each new instance of the parallel gateway sender. -A parallel gateway sender uses multiple queues on multiple Geode members to simultaneously distribute region events to a remote Geode cluster. Each queue distributes only part of the events for a configured region. For example, for a partitioned region, each queue distributes only those events for the local partition. - -Distributed, non-replicated regions can also use a parallel gateway sender for distribution. With a distributed region, Geode creates a separate gateway sender and queue on each member that hosts the region, and then hashes region events to place them into a distinct queue. This provides a level of scalability for distributed regions that is similar to that provided for partitioned regions. - -**Note:** Replicated regions cannot use a parallel gateway sender. -Although parallel gateway senders provide the best throughput for WAN distribution, they provide less control for ordering events. With a parallel gateway sender, you cannot preserve event ordering for the region as a whole because multiple Geode servers distribute the regions events at the same time. However, the ordering of events for a given partition (or in a given queue of a distributed region) can be preserved. See [Configuring Multi-Site (WAN) Event Queues](../../developing/events/configure_multisite_event_messaging.html#configure_multisite_event_messaging). +Although parallel gateway senders provide the best throughput for WAN distribution, they provide less control for event ordering. Event ordering for the region as a whole is not preserved, because multiple Geode servers distribute the regions events at the same time. However, the ordering of events for a given partition can be preserved. See [Configuring Multi-Site (WAN) Event Queues](../../developing/events/configure_multisite_event_messaging.html#configure_multisite_event_messaging). ## Gateway Sender Queues