Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-1498

Diagram in management console for HA (replication, sharedstore) does not reflect real topology

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • AMQ 7.1.1.GA, AMQ 7.2.0.GA
    • high-availability, management
    • None
    • Release Notes
    • If you configure a broker cluster with some extra, passive slaves, the cluster diagram in the web console does not show these passive slaves.
    • Documented as Known Issue

    Description

      Shared store is unable to show proper topology
      By default, it shows some extra "nodes", which are not present + "undefined" node.
      If I had 1 master and 3 slaves (2 were passive slaves), I could not see those passive slaves.

      Similar problem is with replication, but only single slave (passive slaves) is not shown. The rest of the topology looks fine.

      == HA shared store example ==
Search for "amq-172-0-0-." to see that each of the brokers see whole topology correctly. 
Also, slave brokers are not displayed correctly (at all!) - green nodes.
"undefined" brokers are present. 

active M1 172.0.0.5

Topology response
{"request":{"mbean":"org.apache.activemq.artemis:broker=\"amq-172-0-0-5\",component=cluster-connections,name=\"my-cluster\"","attribute":"Topology","type":"read"},"value":"topology on Topology@2aac7380[owner=ClusterConnectionImpl@220695851[nodeUUID=665ea2df-58f5-11e8-9795-fa163e4614e7, connector=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-5, address=, server=ActiveMQServerImpl::serverUUID=665ea2df-58f5-11e8-9795-fa163e4614e7]]:\n\t664b6986-58f5-11e8-a696-fa163ec4c59b => TopologyMember[id = 664b6986-58f5-11e8-a696-fa163ec4c59b, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-15], backupGroupName=null, scaleDownGroupName=null]\n\t665ea2df-58f5-11e8-9795-fa163e4614e7 => TopologyMember[id = 665ea2df-58f5-11e8-9795-fa163e4614e7, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-5, b=null], backupGroupName=null, scaleDownGroupName=null]\n\t664e7627-58f5-11e8-86be-fa163e492946 => TopologyMember[id = 664e7627-58f5-11e8-86be-fa163e492946, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-28], backupGroupName=null, scaleDownGroupName=null]\n\t66583abc-58f5-11e8-ae03-fa163eaaeec4 => TopologyMember[id = 66583abc-58f5-11e8-ae03-fa163eaaeec4, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-27], backupGroupName=null, scaleDownGroupName=null]\n\tnodes=4\tmembers=4","timestamp":1526467625,"status":200}


active S1 172.0.0.27
2018-05-16 12:42:06,575 INFO  [org.apache.activemq.artemis.core.server] AMQ221031: backup announced

{"request":{"mbean":"org.apache.activemq.artemis:broker=\"amq-172-0-0-27\",component=cluster-connections,name=\"my-cluster\"","attribute":"Topology","type":"read"},"value":"topology on Topology@73ce51e9[owner=ClusterConnectionImpl@282263566[nodeUUID=66583abc-58f5-11e8-ae03-fa163eaaeec4, connector=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-27, address=, server=ActiveMQServerImpl::serverUUID=66583abc-58f5-11e8-ae03-fa163eaaeec4]]:\n\t664b6986-58f5-11e8-a696-fa163ec4c59b => TopologyMember[id = 664b6986-58f5-11e8-a696-fa163ec4c59b, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-15], backupGroupName=null, scaleDownGroupName=null]\n\t664e7627-58f5-11e8-86be-fa163e492946 => TopologyMember[id = 664e7627-58f5-11e8-86be-fa163e492946, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-28], backupGroupName=null, scaleDownGroupName=null]\n\t665ea2df-58f5-11e8-9795-fa163e4614e7 => TopologyMember[id = 665ea2df-58f5-11e8-9795-fa163e4614e7, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-5, b=null], backupGroupName=null, scaleDownGroupName=null]\n\t66583abc-58f5-11e8-ae03-fa163eaaeec4 => TopologyMember[id = 66583abc-58f5-11e8-ae03-fa163eaaeec4, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-27], backupGroupName=null, scaleDownGroupName=null]\n\tnodes=4\tmembers=4","timestamp":1526467358,"status":200}


passive S2 172.0.0.15
{"request":{"mbean":"org.apache.activemq.artemis:broker=\"amq-172-0-0-15\",component=cluster-connections,name=\"my-cluster\"","attribute":"Topology","type":"read"},"value":"topology on Topology@5b2a5fb4[owner=ClusterConnectionImpl@1472755462[nodeUUID=664b6986-58f5-11e8-a696-fa163ec4c59b, connector=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-15, address=, server=ActiveMQServerImpl::serverUUID=664b6986-58f5-11e8-a696-fa163ec4c59b]]:\n\t664b6986-58f5-11e8-a696-fa163ec4c59b => TopologyMember[id = 664b6986-58f5-11e8-a696-fa163ec4c59b, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-15], backupGroupName=null, scaleDownGroupName=null]\n\t664e7627-58f5-11e8-86be-fa163e492946 => TopologyMember[id = 664e7627-58f5-11e8-86be-fa163e492946, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-28], backupGroupName=null, scaleDownGroupName=null]\n\t665ea2df-58f5-11e8-9795-fa163e4614e7 => TopologyMember[id = 665ea2df-58f5-11e8-9795-fa163e4614e7, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-5, b=null], backupGroupName=null, scaleDownGroupName=null]\n\t66583abc-58f5-11e8-ae03-fa163eaaeec4 => TopologyMember[id = 66583abc-58f5-11e8-ae03-fa163eaaeec4, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-27], backupGroupName=null, scaleDownGroupName=null]\n\tnodes=4\tmembers=4","timestamp":1526467649,"status":200}

passive S3 172.0.0.28
{"request":{"mbean":"org.apache.activemq.artemis:broker=\"amq-172-0-0-28\",component=cluster-connections,name=\"my-cluster\"","attribute":"Topology","type":"read"},"value":"topology on Topology@6be1f3fe[owner=ClusterConnectionImpl@232687410[nodeUUID=664e7627-58f5-11e8-86be-fa163e492946, connector=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-28, address=, server=ActiveMQServerImpl::serverUUID=664e7627-58f5-11e8-86be-fa163e492946]]:\n\t664b6986-58f5-11e8-a696-fa163ec4c59b => TopologyMember[id = 664b6986-58f5-11e8-a696-fa163ec4c59b, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-15], backupGroupName=null, scaleDownGroupName=null]\n\t664e7627-58f5-11e8-86be-fa163e492946 => TopologyMember[id = 664e7627-58f5-11e8-86be-fa163e492946, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-28], backupGroupName=null, scaleDownGroupName=null]\n\t665ea2df-58f5-11e8-9795-fa163e4614e7 => TopologyMember[id = 665ea2df-58f5-11e8-9795-fa163e4614e7, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-5, b=null], backupGroupName=null, scaleDownGroupName=null]\n\t66583abc-58f5-11e8-ae03-fa163eaaeec4 => TopologyMember[id = 66583abc-58f5-11e8-ae03-fa163eaaeec4, connector=Pair[a=null, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=172-0-0-27], backupGroupName=null, scaleDownGroupName=null]\n\tnodes=4\tmembers=4","timestamp":1526467695,"status":200}

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-1536 Misconfigured HA Shared store shows proper cluster topology, unless started to use properly

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-1700 HA replication Diagram in management console on slaves wrongly identifies itself as master and associated master (depicted as slave) has wrong slave's name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-1478 HA Shared store does not show passive backup nodes at all

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Activity

            People

              gaohoward Howard Gao
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: