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

Provide simpler access to deployed topology of masters, slaves brokers instead of currently used clumsy "Topology" from console

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Critical
    • None
    • AMQ 7.1.0.GA, AMQ 7.1.1.GA
    • management
    • None
    • Documentation (Ref Guide, User Guide, etc.), User Experience

    Description

      Currently in HA deployments, one can hardly figure out programmatically which broker nodes are slaves and which are masters.

      There is one clumsy operation on Jolokia, that displays it, but it's not user friendly at all.

      http://<node>:8161/hawtio/jolokia/read/org.apache.activemq.artemis:broker="<broker-name>,component=cluster-connections,name=<cluster-name>/Topology

      It returns following details

      {"request":{"mbean":"org.apache.activemq.artemis:broker=\"amq-10-37-145-203\",component=cluster-connections,name=\"my-cluster\"","attribute":"Topology","type":"read"},"value":"topology on Topology@c7583e1[owner=ClusterConnectionImpl@1180244251[nodeUUID=47fb0768-32c5-11e8-a450-5254004e96d5, connector=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-203, address=, server=ActiveMQServerImpl::serverUUID=47fb0768-32c5-11e8-a450-5254004e96d5]]:\n\t47fb0768-32c5-11e8-a450-5254004e96d5 => TopologyMember[id = 47fb0768-32c5-11e8-a450-5254004e96d5, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-203, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-205], backupGroupName=fish, scaleDownGroupName=null]\n\t4803ba12-32c5-11e8-b116-5254007f6e6f => TopologyMember[id = 4803ba12-32c5-11e8-b116-5254007f6e6f, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-204, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-214], backupGroupName=fish, scaleDownGroupName=null]\n\t47e7a685-32c5-11e8-aaac-52540045bbb8 => TopologyMember[id = 47e7a685-32c5-11e8-aaac-52540045bbb8, connector=Pair[a=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-202, b=TransportConfiguration(name=artemis, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=10-37-145-223], backupGroupName=fish, scaleDownGroupName=null]\n\tnodes=6\tmembers=3","timestamp":1522270406,"status":200}

      It is really hard to figure out at first (and even second and third) look what nodes are master-slave pairs, who is slave etc. This information is there, but it's not easily accessible.
      On the contrary, there is a nice diagram in console, which depicts current topology, but again - this is not usable for programmatic usage.

      Therefore I would like to see some exposed functions to display slave/master for given broker node and current masters/slaves.

      Attachments

        Issue Links

          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

          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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-807 Console needs a cluster summary view

          • 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

          Activity

            People

              rh-ee-ataylor Andy Taylor
              mtoth@redhat.com Michal Toth
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: