Uploaded image for project: 'AMQ Documentation'
  1. AMQ Documentation
  2. AMQDOC-3077

Customer feedback - [AMQ7, openshift, HA] "High Availability" section improvements.

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Obsolete
    • Icon: Major Major
    • 7.4.0
    • 7.2.0
    • Broker DOC
    • +

      In the "High Availability" section of the "deploying_amq_broker_on_openshift_container_platform" it does NOT state that the HA setup is using a cluster of AMQ7 brokers.

      I would suggest that it should contain the following information:

      1) all the brokers deployed in the pods form a cluster of AMQ brokers

      2) what advantage a cluster of brokers offer, compared to a single broker/pod that is restarted by openshift in the event the pod is stopped.

      Note on point 2. I discussed this briefly with roddiekieley and the advantage is lack of downtime. If multiple pods/brokers are deployed in a broker cluster (on openshift) the client can reconnect to another broker immediately and do not have to wait for the original pod to be restarted.

      However the messages residing on the broker/pod that shutdown will not be available until the pod is restarted or the messages have been "drained" by the "drainer pod".

              jbyrne@redhat.com John Byrne (Inactive)
              rhn-support-pfox Patrick Fox (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: