用于核心桥接器的Artemis HA配置

Question

我们在两个共享磁盘HA对中有4个服务器，它们之间有核心桥接器。在所有4台服务器上，核心桥接器配置和它们使用的连接器（sms和sms1b)是相同的。唯一的区别是主从ha和其他字段中的主机名(acceptor、artemis和node0连接器、name）

<configuration xmlns="urn:activemq"
               xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
               xmlns:xi="http://www.w3.org/2001/XInclude"
               xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd">

   <core xmlns="urn:activemq:core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="urn:activemq:core ">

      <name>ba-artms3.example.com</name>      
      <security-enabled>false</security-enabled>
      <persistence-enabled>true</persistence-enabled>
      <paging-directory>/data/ba_artemis/msg-sms1/paging</paging-directory>
      <bindings-directory>/data/ba_artemis/msg-sms1/bindings</bindings-directory>
      <journal-directory>/data/ba_artemis/msg-sms1/journal</journal-directory>
      <large-messages-directory>/data/ba_artemis/msg-sms1/large-messages</large-messages-directory>

      <journal-datasync>true</journal-datasync>
      <journal-min-files>2</journal-min-files>
      <journal-pool-files>10</journal-pool-files>
      <journal-device-block-size>4096</journal-device-block-size>
      <journal-file-size>10M</journal-file-size>
      <journal-buffer-timeout>132000</journal-buffer-timeout>
      <journal-max-io>4096</journal-max-io>
      <connectors>
            <connector name="artemis">tcp://ba-artms3.example.com:2539</connector>
            <connector name = "node0">tcp://ba-artms4.example.com:2539</connector>
            <connector name="sms1">(tcp://ba-artms3.example.com:61616,tcp://ba-artms4.example.com:61616)</connector>
            <connector name="sms1b">(tcp://ba-artms9.example.com:61616,tcp://ba-artms10.example.com:61616)</connector>
      </connectors>

      <disk-scan-period>5000</disk-scan-period>
      <max-disk-usage>90</max-disk-usage>
      <critical-analyzer>true</critical-analyzer>
      <critical-analyzer-timeout>120000</critical-analyzer-timeout>
      <critical-analyzer-check-period>60000</critical-analyzer-check-period>
      <critical-analyzer-policy>HALT</critical-analyzer-policy>
      <page-sync-timeout>620000</page-sync-timeout>

      <acceptors>
         <acceptor name="artemis">tcp://ba-artms3.example.com:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpDuplicateDetection=true;</acceptor>
         <acceptor name="cluster">tcp://ba-artms3.example.com:2539?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;protocols=CORE;useEpoll=true</acceptor>
         <acceptor name="amqp">tcp://ba-artms3.example.com:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true</acceptor>

      </acceptors>

      <cluster-user>msg-sms1-cluster</cluster-user>

      <cluster-password>redacted</cluster-password>
      <cluster-connections>
         <cluster-connection name="msg-sms1">
            <connector-ref>artemis</connector-ref>
            <message-load-balancing>ON_DEMAND</message-load-balancing>
            <max-hops>0</max-hops>
            <static-connectors>
               <connector-ref>node0</connector-ref>

            </static-connectors>
         </cluster-connection>
      </cluster-connections>

      <ha-policy>
         <shared-store>
            <master>
               <failover-on-shutdown>true</failover-on-shutdown>
            </master>
         </shared-store>
      </ha-policy>

      <security-settings>
         <security-setting match="#">
            <permission type="createNonDurableQueue" roles="amq"/>
            <permission type="deleteNonDurableQueue" roles="amq"/>
            <permission type="createDurableQueue" roles="amq"/>
            <permission type="deleteDurableQueue" roles="amq"/>
            <permission type="createAddress" roles="amq"/>
            <permission type="deleteAddress" roles="amq"/>
            <permission type="consume" roles="amq"/>
            <permission type="browse" roles="amq"/>
            <permission type="send" roles="amq"/>
            <!-- we need this otherwise ./artemis data imp wouldn't work -->
            <permission type="manage" roles="amq"/>
         </security-setting>
      </security-settings>

      <address-settings>

         <address-setting match="activemq.management#">
            <dead-letter-address>DLQ</dead-letter-address>
            <expiry-address>ExpiryQueue</expiry-address>
            <redelivery-delay>0</redelivery-delay>
            <max-size-bytes>-1</max-size-bytes>
            <message-counter-history-day-limit>10</message-counter-history-day-limit>
            <address-full-policy>PAGE</address-full-policy>
            <auto-create-queues>true</auto-create-queues>
            <auto-create-addresses>true</auto-create-addresses>
            <auto-create-jms-queues>true</auto-create-jms-queues>
            <auto-create-jms-topics>true</auto-create-jms-topics>
         </address-setting>
         <address-setting match="#">
            <dead-letter-address>DLQ</dead-letter-address>
            <expiry-address>ExpiryQueue</expiry-address>
            <redelivery-delay>0</redelivery-delay>
            <max-size-bytes>-1</max-size-bytes>
            <message-counter-history-day-limit>10</message-counter-history-day-limit>
            <address-full-policy>PAGE</address-full-policy>
            <auto-create-queues>true</auto-create-queues>
            <auto-create-addresses>true</auto-create-addresses>
            <auto-create-jms-queues>true</auto-create-jms-queues>
            <auto-create-jms-topics>true</auto-create-jms-topics>
         </address-setting>
      </address-settings>

      <xi:include href="${configDir}/addresses.xml"/>

 <bridges>
     <bridge name="sms1_forwarder">
       <queue-name>UpdateOutboundForward_0</queue-name>
       <forwarding-address>UpdateOutbound</forwarding-address>
       <ha>true</ha>
       <failover-on-server-shutdown>true</failover-on-server-shutdown>
       <user>rave</user>
       <password>redacted</password>
       <static-connectors>
         <connector-ref>sms1</connector-ref>
       </static-connectors>
     </bridge>
     <bridge name="sms1b_forwarder">
       <queue-name>UpdateOutboundForward_1</queue-name>
       <forwarding-address>UpdateOutbound</forwarding-address>
       <ha>true</ha>
       <failover-on-server-shutdown>true</failover-on-server-shutdown>
       <user>rave</user>
       <password>redacted</password>
       <static-connectors>
         <connector-ref>sms1b</connector-ref>
       </static-connectors>
     </bridge>
  </bridges>
   </core>
</configuration>

Answer 1

您的配置看起来基本上是正确的，但是很难判断有这么多移动的部分--尤其是用于集群的额外的acceptor。我以前见过这样做的人，但这不是我测试过或推荐过的东西，所以我不确定它在实践中会如何发挥作用。从理论上讲，这是好的，但总有复杂的因素，其中许多是微妙的。

将您的配置简化到只需要重现问题所必需的部分是值得的。例如，只在1台服务器上配置1个桥接器，将本地机器上的所有代理连接到一个活动/备份对，并在唯一端口上（即没有docker）。一旦你有了这样的工作，你可以继续增加复杂性和测试，因为你去看看事情的崩溃（假设他们是）。