Open tzieleniewski opened 2 years ago
Hello there tzieleniewski! 👋
Thank you and congratulations 🎉 for opening your very first issue in this project! 💖
In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀
Hi,
Could you please share:
Howdy,
Please let me know if I can provide more info.
Which version are you using? There's a link to a commit in the upper left corner of the app https://github.com/provectus/kafka-ui/commit/38c4cf7
A screenshot with the topics page with enabled browser console (network tab)?
Thanks. Which kafka are you using? There are some problems with connecting to your cluster:
kafka-ui | org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write a non-default includeSynonyms at version 0
kafka-ui | org.apache.kafka.common.errors.UnsupportedVersionException: The broker does not support DESCRIBE_LOG_DIRS
Thanks. Which kafka are you using? There are some problems with connecting to your cluster:
Howdy we are using 2.8.0
Thanks, we'll take a look into this.
Btw, how do you run the kafka itself? Docker/bare metal? If docker, which image name & version is it?
@Haarolean sorry but I had provided you with wrong version number. I've checked with other tool and it indicated that Kafka version is v0.11.0. Perhaps this is an issue. I got mislead by the version displayed in the application log.
@tzieleniewski oh wow! I wanted to ask you to double check the version, but noticed the same thing in logs as you did and decided not to. Yeaah, that's old as dirt. Would you consider upgrading?
@Haarolean would like that, but it does not depend on us, unfortunately.
thank you and take care
@tzieleniewski supporting such an old version would be a pretty huge load on development, if even possible (I dunno which APIs are present for this version). Unfortunately we don't have a bandwidth for this, but will consider it in the future.
Best wishes!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I think I have the same problem from this post. I've deployed a kafka cluster and I'm doing a test in which I stop one of the brokers. I can reproduce this issue. When I stop one broker, I can see that the only page (far now) that get errors is the [..]/ui/clusters/ClusterDev/topics. In the logs there is:
2022-09-20 18:55:25,425 ERROR [parallel-1] o.s.b.a.w.r.e.AbstractErrorWebExceptionHandler: [0bce61d8-79] 500 Server Error for HTTP GET "/api/clusters/ClusterDev/topics?showInternal=true&search=&orderBy=NAME&sortOrder=ASC" org.apache.kafka.common.errors.TimeoutException: Call(callName=metadata, deadlineMs=1663700125423, tries=591, nextAllowedTryMs=1663700125524) timed out at 1663700125424 after 591 attempt(s) Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: Error has been observed at the following site(s): __checkpoint ⇢ Handler com.provectus.kafka.ui.controller.TopicsController#getTopics(String, Integer, Integer, Boolean, String, TopicColumnsToSortDTO, SortOrderDTO, ServerWebExchange) [DispatcherHandler] checkpoint ⇢ com.provectus.kafka.ui.config.ReadOnlyModeFilter [DefaultWebFilterChain] *checkpoint ⇢ com.provectus.kafka.ui.config.CustomWebFilter [DefaultWebFilterChain] __checkpoint ⇢ org.springframework.security.web.server.authorization.AuthorizationWebFilter [DefaultWebFilterChain] checkpoint ⇢ org.springframework.security.web.server.authorization.ExceptionTranslationWebFilter [DefaultWebFilterChain] *checkpoint ⇢ org.springframework.security.web.server.authentication.logout.LogoutWebFilter [DefaultWebFilterChain] __checkpoint ⇢ org.springframework.security.web.server.savedrequest.ServerRequestCacheWebFilter [DefaultWebFilterChain] checkpoint ⇢ org.springframework.security.web.server.context.SecurityContextServerWebExchangeWebFilter [DefaultWebFilterChain] *checkpoint ⇢ org.springframework.security.web.server.authentication.AuthenticationWebFilter [DefaultWebFilterChain] __checkpoint ⇢ org.springframework.security.web.server.context.ReactorContextWebFilter [DefaultWebFilterChain] checkpoint ⇢ org.springframework.security.web.server.header.HttpHeaderWriterWebFilter [DefaultWebFilterChain] *checkpoint ⇢ org.springframework.security.config.web.server.ServerHttpSecurity$ServerWebExchangeReactorContextWebFilter [DefaultWebFilterChain] __checkpoint ⇢ org.springframework.security.web.server.WebFilterChainProxy [DefaultWebFilterChain] checkpoint ⇢ org.springframework.boot.actuate.metrics.web.reactive.server.MetricsWebFilter [DefaultWebFilterChain] *checkpoint ⇢ HTTP GET "/api/clusters/ClusterDev/topics?showInternal=true&search=&orderBy=NAME&sortOrder=ASC" [ExceptionHandlingWebHandler] Original Stack Trace: Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: metadata
I can confirm with kafkacat that the cluster is operational.
KafkaVersion: 3.2 (Deployed with strimzi) Kafka-ui: 0.4 (Deployed with helm)
@rafaeldomi hey, that's unrelated, you have a pretty new kafka. Please take a look at #2103, if that's the same issue you experience -- please leave a comment there, if not -- please raise a new one.
@Haarolean Hi, do you have any plans about support older kafka version, like 0.11.0
@newsbreak-tonglin it's nowhere close to our priority list considering this would require major changes across the whole application's codebase.
@newsbreak-tonglin it's nowhere close to our priority list considering this would require major changes across the whole application's codebase.
Hi, I have a similar problem with kafka2.11_1.0.1:
org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write a non-default includeSynonyms at version 0
We need to clarify the usage rules of kafka-ui within our team. Is it possible to clarify the earliest version number of kafka currently supported by kafka-ui? Is it only available for kafka2 or above?
@kukayiyi hi, 2.x should work fine, yes.
Describe the bug There is no topic list displayed. But when I display the consumers list I am able to navigate to topic for this consumer group.
There is a warning in logs
Set up Version:0.3.3 Run through docker compose
Steps to Reproduce
Expected behavior See list of topics.
Logs
Additional context