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

[OpenShift, Broker Operator] First broker in cluster doesn't stop reconnection attempts to non-existent broker, despite default configuration

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Critical
    • None
    • AMQ 7.5.0.GA, 7.5.0.CR3
    • clustering
    • None
    • Hide

      1) AWS deployed OCP4.1 with Broker pods deployed through Broker operator
      2) Scaleup applied using configuraiton change and 

      oc apply -f

      3) Experience bug # ENTMQBR-2942

      Expected:
      After 10 tries, other pods stop trying to connect to non-existent pod from bug ENTMQBR-2942

      Real:
      It still continues trying to connect to pod after 10 tries, indefinitely.

      Show
      1) AWS deployed OCP4.1 with Broker pods deployed through Broker operator 2) Scaleup applied using configuraiton change and oc apply -f 3) Experience bug # ENTMQBR-2942 Expected: After 10 tries, other pods stop trying to connect to non-existent pod from bug ENTMQBR-2942 Real: It still continues trying to connect to pod after 10 tries, indefinitely.

    Attachments

      Issue Links

        is related to

        Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-2942 Operator scaleup to n Pods: Pod #0 tries to contact non-existent Pod #n+1

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed

        Activity

          People

            rhn-support-rkieley Roderick Kieley
            mkrutov Mikhail Krutov
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: