Replies: 6 comments
-
For a start, you have to provide more details about the supposed bug:
|
Beta Was this translation helpful? Give feedback.
-
Sure. Here is the apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnector
metadata:
labels:
strimzi.io/cluster: debezium-connect-cluster
name: debezium-connector-mysql
namespace: connector-testing
spec:
class: io.debezium.connector.mysql.MySqlConnector
config:
database.history.kafka.bootstrap.servers: debezium-cluster-kafka-bootstrap:9092
database.history.kafka.topic: schema-changes
database.server.name: mysql
tasksMax: 1
status:
conditions:
- lastTransitionTime: "2024-01-02T20:08:23.962570749Z"
message: KafkaConnect resource 'debezium-connect-cluster' identified by label
'strimzi.io/cluster' does not exist in namespace connector-testing.
reason: NoSuchResourceException
status: "True"
type: NotReady
observedGeneration: 1
tasksMax: 0
After detecting problem with the operator, we recreated the object that didn't have the apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnector
metadata:
labels:
strimzi.io/cluster: debezium-connect-cluster
name: debezium-connector-mysql
namespace: connector-testing
spec:
class: io.debezium.connector.mysql.MySqlConnector
config:
database.history.kafka.bootstrap.servers: debezium-cluster-kafka-bootstrap:9092
database.history.kafka.topic: schema-changes
database.server.name: mysql
tasksMax: 1
The operator log is attached. It has logs only for two days. |
Beta Was this translation helpful? Give feedback.
-
I guess you should try to restart the cluster operator: you seem to have some stuck reconciliations:
You should also consider upgrading as we fixed some related bugs since 0.35. But not sure that is related to the problem you describe here. As for the connector ... you seemto have the connector created in the namespace |
Beta Was this translation helpful? Give feedback.
-
Regarding what you mentioned about the connector and its namespace, I'm pretty sure that it's not the problem since the object had status (the operator did the reconciliation) before needing the operator to be restarted. Additionally, I just provided one of the connector objects. We had others that were in the same cluster that Kafka and Kafka connect were available, but the same issue happened: No reconciliation, hence, no status. BTW, we'll consider the operator upgrade; we hope it will resolve the issue. |
Beta Was this translation helpful? Give feedback.
-
Well, you should probably elaborate on why you think it is not a problem. The log you shared shows you do not have the matching Kafka Connect cluster in that namespace. |
Beta Was this translation helpful? Give feedback.
-
Triaged on a community call on 1.11.2024: Does not look like a Strimzi bug. It should be converted to discussion where we can continue with it. |
Beta Was this translation helpful? Give feedback.
-
Bug Description
We have installed the Strimzi operator on our cluster and created some objects including the
Kafka
cluster,Kafkaconnect
, and someKafkaConnectors
. However, after a couple of months, Kafka Connectors weren't reconciled anymore. We noticed that by checking the status of the newly created connectors in which there wasn't any status field meaning that the reconciliation didn't happen for them. Objects like Kafka and kafkaconnects were reconciled properly but not the same for Kafkaconnectors.Additionally, there wasn't any record regarding the connectors in the operator log.
Finally, the issue was resolved after restarting the operator but we're worried about this problem in the future since it needs our manual action for restarting the operator pod.
It seems that it could be related to
futures
mentioned in here and #5691.Steps to reproduce
Kafka
,KafkaConnect
,KafkaConnector
.KafkaConnector
objects anymore.Expected behavior
The operator must always reconcile all objects, no matter how many objects are already existed there.
Strimzi version
0.35.1
Kubernetes version
Openshift 4.10
Installation method
OperatorHub.io
Infrastructure
No response
Configuration files and logs
No response
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions