All data gone - topics deleted themselves (I think) #4470
Unanswered
Brandt1930
asked this question in
Q&A
Replies: 1 comment 4 replies
-
Well, this error:
Means the KafkaTopic CRD does not exist anymore. So someone / something deleted it and that also deleted all the topics (when the CRD is deleted it normally deletes all the CRs). |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a Kubernetes Cluster (GitVersion 1.19.6, on OpenSuse Linux) running on 5 node (one of which is master-node) with the latest Strimzi. Inside we have mutliple Namespaces with 3-Node-Kafka-ZK-Clusters. Yesterday everything worked fine, today I entered the office and everything was gone... no Topics (only the Strimzi ones, and __custormer_offset), no data on the PV's (checked the hard drives)..
I still cant figure out why so any help is appreciated.
Some log extracts here (example Topic mqtt-raw):
The logs in /var/log/pods/ are starting with a reboot at 7:37, everything loads fine:
"log":"2021-02-24 08:06:00,488 INFO [Partition mqtt-raw-0 broker=0] Log loaded for partition mqtt-raw-0 with initial high watermark 19374 (kafka.cluster.Partition) [data-plane-kafka-request-handler-3]\n","strea m":"stdout","time":"2021-02-24T08:06:00.488242293Z"}
But some seconds later seemingly out of nowhere:
{"log":"2021-02-24 08:06:09,706 TRACE [Broker id=0] Deleted partition mqtt-raw-0 from metadata cache in response to UpdateMetadata request sent by controller 2 epoch 4 with correlation id 30 (state.change.logger) [data-plane-kafka-request-handler-1]\n","stream":"stdout","time":"2021-02-24T08:06:09.706708403Z"}
And then some seconds later it is marked as deleted and its gone..
Also, the entity-topic-operator doesnt work anymore the logs say:
I know my data is gone but I want to understand whats going on
Beta Was this translation helpful? Give feedback.
All reactions