Strimzi
Topic Operator doesn't show entire list of Topics #8845
Replies: 11 comments
-
|
Please provide more details. For example:
|
Beta Was this translation helpful? Give feedback.
-
|
Using the operator CRD's for each Topic there is kafatopic yaml definition and we observed few topics are missing. We tried to list Topics using /opt/bitnami/kafka/bin/kafka-topics.sh and the list of Topics doesn't match which shows in Kafka-Topic Operator. Few topics that are missing: devicemanagement.datarequest.highres |
Beta Was this translation helpful? Give feedback.
-
|
The log is not complete. So it is hard to say anything based on it. But in any case it says that It does not mention the other one, but as long as the log is not complete, it does not mean anything, |
Beta Was this translation helpful? Give feedback.
-
|
Actually, the one in the log has the |
Beta Was this translation helpful? Give feedback.
-
|
strimzi-topic-operator-7897d7778b-9kf9t.log |
Beta Was this translation helpful? Give feedback.
-
|
couldn't figure out why Topic Operator couldn't discover the missing topics . |
Beta Was this translation helpful? Give feedback.
-
|
Well, the full log might give some explanation. That is why I was asking for it. |
Beta Was this translation helpful? Give feedback.
-
|
strimzi-topic-operator-7897d7778b-2dv5z.log Here are the full logs |
Beta Was this translation helpful? Give feedback.
-
|
That starts at the beginning. But it seems to run only for a short time and not complete the initial load maybe? So while the previous logs were missing the start this one is possibly missing the end? If it did complete the initial load, it seems the Kafka Admin API is not returning these topics. Does it have the right for them? Are the topics somehow special? (e.g. different configuration) |
Beta Was this translation helpful? Give feedback.
-
|
Compared the missing Topic configurations with listed one's and i dind't find anything abnormal and i dont see ACL's being applied as well. |
Beta Was this translation helpful? Give feedback.
-
|
we are using Amazon Managed Streaming for Apache Kafka (Amazon MSK) cluster. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Please use this to only for bug reports. For questions or when you need help, you can use the GitHub Discussions, our #strimzi Slack channel or out user mailing list.
Describe the bug
Using Strimzi Topic Operator the number of topics that were listed doesn't match that are on MSK cluster.
To Reproduce
Steps to reproduce the behavior:
we use Kafdrop to list the number of topic.
Count using Kafdrop is different from Strimzi Topic Operator.
Expected behavior
A clear and concise description of what you expected to happen.
we expect topics should match using both tools.
Environment (please complete the following information):
YAML files and logs
Attach or copy paste the custom resources you used to deploy the Kafka cluster and the relevant YAMLs created by the Cluster Operator.
Attach or copy and paste also the relevant logs.
To easily collect all YAMLs and logs, you can use our report script which will automatically collect all files and prepare a ZIP archive which can be easily attached to this issue.
The usage of this script is:
./report.sh --namespace <string> --cluster <string> [--bridge <string>] [--connect <string>] [--mm2 <string>]Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions