[activemq-artemis] branch master updated: NO-JIRA remove failover-on-server-shutdown from bridge doc

[cl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

clebertsuconic pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git


The following commit(s) were added to refs/heads/master by this push:
     new 86cb888  NO-JIRA remove failover-on-server-shutdown from bridge doc
     new 2697253  This closes #3437
86cb888 is described below

commit 86cb888b625626108539e09729f694030f337191
Author: Justin Bertram <jb...@apache.org>
AuthorDate: Sun Feb 7 14:48:13 2021 -0600

    NO-JIRA remove failover-on-server-shutdown from bridge doc
---
 .../src/main/resources/schema/artemis-configuration.xsd |  4 +++-
 docs/user-manual/en/core-bridges.md                     | 17 -----------------
 2 files changed, 3 insertions(+), 18 deletions(-)

diff --git a/artemis-server/src/main/resources/schema/artemis-configuration.xsd b/artemis-server/src/main/resources/schema/artemis-configuration.xsd
index 8cc56c7..6bf6097 100644
--- a/artemis-server/src/main/resources/schema/artemis-configuration.xsd
+++ b/artemis-server/src/main/resources/schema/artemis-configuration.xsd
@@ -1589,7 +1589,9 @@
          <xsd:element name="failover-on-server-shutdown" type="xsd:boolean" default="false" maxOccurs="1" minOccurs="0">
             <xsd:annotation>
                <xsd:documentation>
-                  should failover be prompted if target server is cleanly shutdown?
+                  DEPRECATED: This setting has no impact, but it's being left here to avoid XML parsing errors for users
+                  who still have it set. Failover on shutdown is controlled via the ha-policy set on the *broker* to
+                  which the bridge connects.
                </xsd:documentation>
             </xsd:annotation>
          </xsd:element>
diff --git a/docs/user-manual/en/core-bridges.md b/docs/user-manual/en/core-bridges.md
index ebc827c..d51e0bd 100644
--- a/docs/user-manual/en/core-bridges.md
+++ b/docs/user-manual/en/core-bridges.md
@@ -132,23 +132,6 @@ Let's take a look at all the parameters in turn:
   value of `-1` signifies an unlimited number of attempts. The default value is
   `-1`.
 
-- `failover-on-server-shutdown`. This optional parameter determines whether the
-  bridge will attempt to failover onto a backup server (if specified) when the
-  target server is cleanly shutdown rather than crashed.
-
-  The bridge connector can specify both a live and a backup server, if it
-  specifies a backup server and this parameter is set to `true` then if the
-  target server is *cleanly* shutdown the bridge connection will attempt to
-  failover onto its backup. If the bridge connector has no backup server
-  configured then this parameter has no effect.
-
-  Sometimes you want a bridge configured with a live and a backup target
-  server, but you don't want to failover to the backup if the live server is
-  simply taken down temporarily for maintenance, this is when this parameter
-  comes in handy.
-
-  The default value for this parameter is `false`.
-
 - `use-duplicate-detection`. This optional parameter determines whether the
   bridge will automatically insert a duplicate id property into each message
   that it forwards.