Issue
You may see a constantly loading symbol on one or more of your Kafka clusters.
This Knowledge Base article shows you where to check that your Kafka cluster information is being indexed correctly.
The following pages on Conduktor Console require some information in order to be computed, Topic lists, Consumer Groups/Lists, Schema Lists and Connector Lists, for example, the count of messages on a Topic. To avoid making this call every time a user goes to these pages, Conduktor Console indexes this information at regular intervals.
This indexing works in the following manner:
- New resources will be rendered when you go to a page but some data may need to wait for the indexing to be rendered, e.g. the count of messages.
- When you go to a list, e.g. list of topics, if the data indexed is too old or not completely indexed then the Console is going to perform these actions directly on the Kafka cluster which can lead to slowness.
If you experience slowness it is likely that the data is not indexed and/or too old, please see below how to find further information on the state of indexing each Kafka cluster that you have connected to Conduktor Console.
Troubleshooting
To help troubleshoot go into the Postgres database you are using with Conduktor Console and go to the table index_runs where you will find the last_success_at column.
If the cluster/clusters have an issue with the indexer, the date should be old or missing here. Considered old can be somewhat subjective here depending on the size of clusters but typically we would expect a default of every 30s with a cluster parallelism of 1.
See the example below on a Conduktor Console instance with two clusters. Running the command select * from cdk_governance_metadata.index_runs;
We can see the last_success_at was about a minute or so beforehand which we expect.
If you see issues with missing data or very old last_success_at then you may have a problem with connectivity to Kafka itself or on Conduktor Console.
Please reach out to Consuktor Support if needed,
Comments
0 comments
Please sign in to leave a comment.