You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by cl...@apache.org on 2019/04/24 18:42:38 UTC

[activemq-artemis] branch master updated: NO-JIRA Fix references to failover-on-shutdown in documentation

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 8fe61d2  NO-JIRA Fix references to failover-on-shutdown in documentation
     new 838651c  This closes #2637
8fe61d2 is described below

commit 8fe61d27fb618c462d80a2863a85f623bee49e88
Author: Sebastian Lövdahl <sl...@hibox.fi>
AuthorDate: Wed Apr 24 13:13:53 2019 +0300

    NO-JIRA Fix references to failover-on-shutdown in documentation
---
 docs/user-manual/en/ha.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/user-manual/en/ha.md b/docs/user-manual/en/ha.md
index a9f0517..672e704 100644
--- a/docs/user-manual/en/ha.md
+++ b/docs/user-manual/en/ha.md
@@ -447,7 +447,7 @@ automatically by setting the following property in the
 The following table lists all the `ha-policy` configuration elements for
 HA strategy shared store for `master`:
 
-- `failover-on-server-shutdown`
+- `failover-on-shutdown`
 
   If set to true then when this server is stopped normally the backup will become live assuming failover. If false then the backup server will remain passive. Note that if false you want failover to occur the you can use the the management API as explained at [Management](management.md).
 
@@ -458,7 +458,7 @@ HA strategy shared store for `master`:
 The following table lists all the `ha-policy` configuration elements for
 HA strategy Shared Store for `slave`:
 
-- `failover-on-server-shutdown`
+- `failover-on-shutdown`
 
   In the case of a backup that has become live. then when set to true then when this server is stopped normally the backup will become liveassuming failover. If false then the backup server will remain passive. Note that if false you want failover to occur the you can use the the management API as explained at [Management](management.md).