geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kmil...@apache.org
Subject [geode] branch develop updated: GEODE-3761 Document manual-start deprecation of gateway senders (#895)
Date Tue, 10 Oct 2017 00:14:30 GMT
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 4312158  GEODE-3761 Document manual-start deprecation of gateway senders (#895)
4312158 is described below

commit 43121586774f7d85af88b2547ba27eaa908e63e0
Author: Karen Miller <karensmolermiller@users.noreply.github.com>
AuthorDate: Mon Oct 9 17:14:28 2017 -0700

    GEODE-3761 Document manual-start deprecation of gateway senders (#895)
---
 .../reference/topics/gfe_cache_xml.html.md.erb       |  4 ++--
 .../gfsh/command-pages/create.html.md.erb            |  2 +-
 .../setting_up_a_multisite_system.html.md.erb        | 20 --------------------
 3 files changed, 3 insertions(+), 23 deletions(-)

diff --git a/geode-docs/reference/topics/gfe_cache_xml.html.md.erb b/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
index 3a941eb..c404e99 100644
--- a/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
+++ b/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
@@ -294,8 +294,8 @@ When distributing region events from the local queue, multiple dispatcher
thread
 </tr>
 <tr class="even">
 <td>manual-start</td>
-<td>Boolean value that specifies whether you need to manually start the gateway sender.
If you supply a null value, the default is &quot;false&quot; and the gateway sender
attempts to start automatically.</td>
-<td>null (false)</td>
+<td><b>Deprecated.</b> Boolean value that specifies whether you need to
manually start the gateway sender. If you supply a null value, the default value of false
is used, and the gateway sender attempts to start automatically. <em>A manual start
is likely to cause data loss, so manual start should never be used.</em></td>
+<td>false</td>
 </tr>
 <tr class="odd">
 <td>socket-buffer-size</td>
diff --git a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
index 2fd6841..d620866 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
@@ -523,7 +523,7 @@ create gateway-sender --id=value --remote-distributed-system-id=value
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-manual-start</span></td>
-<td>Boolean value that specifies whether you need to manually start the gateway sender.
If you supply a null value, the default is &quot;false&quot; and the gateway sender
starts automatically.</td>
+<td><b>Deprecated.</b> Boolean value that specifies whether you need to
manually start the gateway sender. If you supply a null value, the default value of false
is used, and the gateway sender starts automatically. <em>A manual start is likely to
cause data loss, so manual start should never be used.</em></td>
 <td>false</td>
 </tr>
 <tr class="even">
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 1890733..174a136 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
@@ -153,27 +153,7 @@ See [WAN Configuration](../../reference/topics/elements_ref.html#topic_7B1CABCAD
         See [Configuring Dispatcher Threads and Order Policy for Event Distribution](../../developing/events/configuring_gateway_concurrency_levels.html#concept_6C52A037E39E4FD6AE4C6A982A4A1A85).
     -   For serial gateway senders (parallel=false) that use multiple `dispatcher-threads`,
also configure the ordering policy to use for dispatching the events. See [Configuring Dispatcher
Threads and Order Policy for Event Distribution](../../developing/events/configuring_gateway_concurrency_levels.html#concept_6C52A037E39E4FD6AE4C6A982A4A1A85).
     -   Determine whether you should conflate events in the queue. See [Conflating Events
in a Queue](../../developing/events/conflate_multisite_gateway_queue.html#conflate_multisite_gateway_queue).
-    -   Decide whether the gateway sender should start automatically or requires a manual
start. This is controlled by the `manual-start` attribute. For example, in gfsh:
 
-        ``` pre
-        gfsh>create gateway-sender --id=sender2 --parallel=true --remote-distributed-system-id=2
--manual-start=true
-        ```
-
-        In cache.xml:
-
-        ``` pre
-        <gateway-sender id="sender2" parallel="false"
-         remote-distributed-system-id="2" 
-         dispatcher-threads="2" order-policy="partition" manual-start="true" />
-        ```
-
-        By default, `manual-start` is set to false on gateway senders and the senders are
started automatically.
-
-4.  If you have configured the gateway sender with `manual-start` equal to true, then start
the gateway sender when appropriate. For persistent gateway senders, the appropriate time
to start them is when all other members hosting persistent regions are started. In gfsh:
-
-    ``` pre
-    gfsh> start gateway-sender --id=sender2
-    ```
 
 **Note:**
 The gateway sender configuration for a specific sender `id` must be identical on each <%=vars.product_name%>
member that hosts the gateway sender.

-- 
To stop receiving notification emails like this one, please contact
['"commits@geode.apache.org" <commits@geode.apache.org>'].

Mime
View raw message