Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broker version doesn't change without kafka ui restart #3749

Closed
4 tasks done
timchenko-a opened this issue Apr 28, 2023 · 2 comments · Fixed by #3764
Closed
4 tasks done

Broker version doesn't change without kafka ui restart #3749

timchenko-a opened this issue Apr 28, 2023 · 2 comments · Fixed by #3764
Assignees
Labels
scope/backend status/accepted An issue which has passed triage and has been accepted type/enhancement En enhancement to an already existing feature
Projects
Milestone

Comments

@timchenko-a
Copy link

timchenko-a commented Apr 28, 2023

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

Kafka UI doesn't automatically update broker version information is case of broker is updated. It requires kafka ui restart.

Expected behavior

Broker is updated -> kafka ui automatically detects new version.

Your installation details

  1. Kafka UI version: ef0dacb v0.6.1
  2. No, I run just like a plain jar on EC2, systemd managed.
  3. The next command is used to run kafka-ui:
    java -Xmx512M -Xms512M -Dspring.config.additional-location=/opt/config.yaml --add-opens java.rmi/javax.rmi.ssl=ALL-UNNAMED -jar /opt/kafka-ui.jar
    /opt/config.yaml content(only 1 cluster here, we have more, but config is pretty much the same everywhere):
---
kafka:
  clusters:
    - name: CLUSTER_NAME
      bootstrapServers: SERVER_1_URL:9093,SERVER_2_URL:9093,SERVER_3_URL:9093
      readonly: true
      properties:
        security:
          protocol: SASL_PLAINTEXT
        sasl:
          mechanism: SCRAM-SHA-256
          jaas:
            config: 'org.apache.kafka.common.security.scram.ScramLoginModule required username="USERNAME" password="PASSWORD";'
      schemaRegistry: http://SCHEMA_REGISTRY_URL:8081

Steps to reproduce

Setup kafka cluster, non-latest version;
Add it to kafka UI. It will detect cluster's version correctly;
Upgrade kafka cluster;
Check broker version in kafka UI, it will stay the same;
Restart kafka UI, now new broker version will be detected.

Screenshots

No response

Logs

No response

Additional context

Want to understand it it's a bug, or an expected behaviour :)

@timchenko-a timchenko-a added status/triage Issues pending maintainers triage type/bug Something isn't working labels Apr 28, 2023
@github-actions
Copy link

Hello there timchenko-a! 👋

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. 👀

@iliax iliax linked a pull request May 2, 2023 that will close this issue
13 tasks
@iliax iliax self-assigned this May 2, 2023
@iliax
Copy link
Contributor

iliax commented May 2, 2023

Hello @timchenko-a , thank you for raising it
can't say that it is a bug, but its better to update version (and version-related) info from time to time.
will be implemented within #3764

@Haarolean Haarolean added type/enhancement En enhancement to an already existing feature status/accepted An issue which has passed triage and has been accepted and removed type/bug Something isn't working status/triage Issues pending maintainers triage labels May 3, 2023
@Haarolean Haarolean added this to the 0.7 milestone May 3, 2023
@Haarolean Haarolean added this to To do in Release 0.7 via automation May 3, 2023
@Haarolean Haarolean moved this from To do to Review in progress in Release 0.7 May 5, 2023
Release 0.7 automation moved this from Review in progress to Done May 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/backend status/accepted An issue which has passed triage and has been accepted type/enhancement En enhancement to an already existing feature
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants