-
Bug
-
Resolution: Done
-
Major
-
1.4.0.GA
-
None
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.
- is related to
-
-
- Closed
-
