strimzi-kafka-operator: cluster-operator service Failed
2020-11-18 09:32:44 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-system...
2020-11-18 09:33:06 INFO OperatorWatcher:40 - Reconciliation #290(watch) Kafka(kafka-system/spider-kafka): Kafka spider-kafka in namespace kafka-system was ADDED
2020-11-18 09:33:16 WARN AbstractOperator:377 - Reconciliation #290(watch) Kafka(kafka-system/spider-kafka): Failed to acquire lock lock::kafka-system::Kafka::spider-kafka within 10000ms.
2020-11-18 09:33:21 ERROR Util:124 - Exceeded timeout of 300000ms while waiting for StatefulSet resource spider-kafka-kafka in namespace kafka-system to be ready
2020-11-18 09:33:21 ERROR AbstractOperator:238 - Reconciliation #286(watch) Kafka(kafka-system/spider-kafka): createOrUpdate failed
io.strimzi.operator.common.operator.resource.TimeoutException: Exceeded timeout of 300000ms while waiting for StatefulSet resource spider-kafka-kafka in namespace kafka-system to be ready
at io.strimzi.operator.common.Util$1.lambda$handle$1(Util.java:125) ~[io.strimzi.operator-common-0.20.0.jar:0.20.0]
at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:327) ~[io.vertx.vertx-core-3.9.1.jar:3.9.1]
at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:366) ~[io.vertx.vertx-core-3.9.1.jar:3.9.1]
at io.vertx.core.impl.EventLoopContext.lambda$executeAsync$0(EventLoopContext.java:38) ~[io.vertx.vertx-core-3.9.1.jar:3.9.1]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) [io.netty.netty-transport-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at java.lang.Thread.run(Thread.java:834) [?:?]
2020-11-18 09:33:22 INFO OperatorWatcher:40 - Reconciliation #291(watch) Kafka(kafka-system/spider-kafka): Kafka spider-kafka in namespace kafka-system was MODIFIED
2020-11-18 09:33:22 WARN AbstractOperator:470 - Reconciliation #286(watch) Kafka(kafka-system/spider-kafka): Failed to reconcile
io.strimzi.operator.common.operator.resource.TimeoutException: Exceeded timeout of 300000ms while waiting for StatefulSet resource spider-kafka-kafka in namespace kafka-system to be ready
at io.strimzi.operator.common.Util$1.lambda$handle$1(Util.java:125) ~[io.strimzi.operator-common-0.20.0.jar:0.20.0]
at io.vertx.core.impl.ContextImpl.lambda$null$0(ContextImpl.java:327) ~[io.vertx.vertx-core-3.9.1.jar:3.9.1]
at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:366) ~[io.vertx.vertx-core-3.9.1.jar:3.9.1]
at io.vertx.core.impl.EventLoopContext.lambda$executeAsync$0(EventLoopContext.java:38) ~[io.vertx.vertx-core-3.9.1.jar:3.9.1]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) [io.netty.netty-transport-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty.netty-common-4.1.50.Final.jar:4.1.50.Final]
at java.lang.Thread.run(Thread.java:834) [?:?]
2020-11-18 09:33:22 WARN AbstractOperator:96 - Kafka resource spider-kafka in namespace kafka-system: In API version kafka.strimzi.io/v1beta1 the property affinity at path spec.zookeeper.affinity has been deprecated. This feature should now be configured at path spec.zookeeper.template.pod.affinity.
2020-11-18 09:33:22 WARN AbstractOperator:139 - Kafka resource spider-kafka in namespace kafka-system: Contains object at path spec.kafka.listeners.genericKafkaListeners with an unknown property: useServiceDnsDomain
2020-11-18 09:33:22 WARN AbstractOperator:96 - Kafka resource spider-kafka in namespace kafka-system: In API version kafka.strimzi.io/v1beta1 the property affinity at path spec.kafka.affinity has been deprecated. This feature should now be configured at path spec.kafka.template.pod.affinity.
2020-11-18 09:33:22 WARN AbstractOperator:96 - Kafka resource spider-kafka in namespace kafka-system: In API version kafka.strimzi.io/v1beta1 the property externalTrafficPolicy at path spec.kafka.template.externalBootstrapService.externalTrafficPolicy has been deprecated.
2020-11-18 09:33:22 WARN AbstractOperator:96 - Kafka resource spider-kafka in namespace kafka-system: In API version kafka.strimzi.io/v1beta1 the property affinity at path spec.zookeeper.affinity has been deprecated. This feature should now be configured at path spec.zookeeper.template.pod.affinity.
2020-11-18 09:33:22 WARN AbstractOperator:139 - Kafka resource spider-kafka in namespace kafka-system: Contains object at path spec.kafka.listeners.genericKafkaListeners with an unknown property: useServiceDnsDomain
version 0.20.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (9 by maintainers)
The address it is connecting to is correct. This is how statefulsets and headless services work. I do not think we changed anything what could affect this in 0.20.0.
@Juandavi1 In your case it looks like some DNS issue. The Zookeeper nodes cannot resolve the DNS addresses and form the cluster. But I’m afraid Kubernetes DNS goes a bit beyond my know-how.