Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-1888

The CR of a topic returns the wrong status after changing the value of min.insync.replicas

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.4.0.GA
    • Fix Version/s: 1.5.0.GA
    • Component/s: topic-operator
    • Labels:
      None

      Description

      When we change the value of "min.insync.replicas" to x, the CR returns an error message and after 1 min the status changes to "Ready":

      For example: we have a healthy KafkaTopic:

      spec:
        config:
          message.format.version: 2.2-IV1
          min.insync.replicas: 1
        partitions: 1
        replicas: 5
        topicName: kafka.test-update-config
      

      When we change the config.min.insync.replicas to "x" we get the following state:

      spec:
        config:
          message.format.version: 2.2-IV1
          min.insync.replicas: x
        partitions: 1
        replicas: 5
        topicName: kafka.test-update-config
      status:
        conditions:
          - lastTransitionTime: '2020-04-27T06:53:30.591Z'
            message: >-
              Invalid config value for resource ConfigResource(type=TOPIC,
              name='kafka.test-update-config'): Invalid value x for configuration
              min.insync.replicas: Not a number of type INT
            reason: InvalidRequestException
            status: 'True'
            type: NotReady
        observedGeneration: 2
      

      This seems fine. But after a minute the state changes to "ready":

      spec:
        config:
          message.format.version: 2.2-IV1
          min.insync.replicas: x
        partitions: 1
        replicas: 5
        topicName: kafka.test-update-config
      status:
        conditions:
          - lastTransitionTime: '2020-04-27T06:54:03.398Z'
            status: 'True'
            type: Ready
        observedGeneration: 2
      

      But the min.insync.replicas is definitly not "x" within Kafka.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              ppatiern Paolo Patierno
              Reporter:
              rhn-support-aboucham Abel Bouchama
              Tester:
              Lukas Kral Lukas Kral
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: