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

Having both global & local operator available during scaledown operation leads to weird behaviour

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • AMQ 7.9.2.GA
    • operator
    • None
    • False
    • False
    • Hide
      1. create local operator
      2. create global operator
      3. deploy ss size=4
      4. scale down to 1, observe
      5. operator-scaledown-weirdness.log
      Show
      create local operator create global operator deploy ss size=4 scale down to 1, observe operator-scaledown-weirdness.log

      It was observed that having both local & global operator available during scaledown leads to two cycles of scaledown: first all of the pods in SS are restarted and then actual scaledown happens. see attached log for details on local operator side.

        1. operator-scaledown-weirdness.log
          288 kB

            gaohoward Howard Gao
            mkrutov Mikhail Krutov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: