[
https://issues.apache.org/jira/browse/ARTEMIS-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
clebert suconic updated ARTEMIS-85:
-----------------------------------
Fix Version/s: (was: 1.5.0)
1.6.0
> Add support for HA cluster / failover discovery using DNS SRV records
> ---------------------------------------------------------------------
>
> Key: ARTEMIS-85
> URL: https://issues.apache.org/jira/browse/ARTEMIS-85
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.0.0
> Reporter: Daniel Pocock
> Fix For: 1.6.0
>
>
> Copied from HORNETQ-1270
> The DNS SRV record provides a convenient and well known mechanism to
> configure active-active, load balanced clusters and to provide failover
> information.
> It is convenient for many people because they already have DNS servers and
> support staff are usually familiar with the procedures for maintaining the
> DNS entries.
> DNS SRV also allows port numbers to be advertised.
> The clustering support using UDP multicast doesn't work for all sites,
> especially where the user is more concerned with failover than load-balancing.
> A specific DNS SRV implementation may involve some or all of the following:
> - clients discovering a HornetQ, JNDI or STOMP host and port
> - servers dynamically deciding which IPs and ports to bind to by checking DNS
> SRV records
> - servers dynamically deciding which other servers to cluster with by
> checking for DNS SRV records
> DNS SRV records may look like this:
> _stomp._tcp.test-mq.example.org. IN SRV 1 50 5566 testmqhost1.example.org.
> _stomp._tcp.test-mq.example.org. IN SRV 2 50 5566 testmqbackup.example.org.
> A STOMP client would then be configured with just the domain name
> "test-mq.example.org" and it would dynamically discover the hosts and ports
> from DNS
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
