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

Don't show active controller for KRaft clusters #525

Open
2 tasks done
bachmanity1 opened this issue Aug 20, 2024 · 1 comment
Open
2 tasks done

Don't show active controller for KRaft clusters #525

bachmanity1 opened this issue Aug 20, 2024 · 1 comment
Labels
area/brokers Broker / broker configs related issues scope/backend Related to backend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature

Comments

@bachmanity1
Copy link
Contributor

bachmanity1 commented Aug 20, 2024

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

No response

Describe the feature you're interested in

For clusters running in KRaft mode, the describe cluster API currently returns any alive broker's ID as controller ID Link to code. I believe this was done because, before KIP-919, clients couldn’t directly communicate with controllers and had to connect through brokers, making the specific broker ID irrelevant. Given this, perhaps for KRaft clusters, it might be better not to display the active controller indicator (and the green tick in front of the broker ID) to avoid confusing users?

Alternatively, in addition to the broker list, it might be helpful to also display the controller list by calling the describe cluster API with EndpointType set to 2. Or perhaps this could be displayed as a single list, since some nodes may have both broker and controller roles. In this scenario, displaying the active controller would make sense.

Describe alternatives you've considered

No response

Version you're running

1.0.0

Additional context

No response

@bachmanity1 bachmanity1 added status/triage Issues pending maintainers triage type/feature A brand new feature labels Aug 20, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Aug 20, 2024
@Haarolean Haarolean added type/enhancement En enhancement/improvement to an already existing feature scope/backend Related to backend changes area/brokers Broker / broker configs related issues and removed type/feature A brand new feature status/triage/manual Manual triage in progress labels Aug 20, 2024
@bachmanity1
Copy link
Contributor Author

@Haarolean, do you plan to remove the active controller from the UI for KRaft clusters, or do you plan to include the controller nodes as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/brokers Broker / broker configs related issues scope/backend Related to backend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Projects
Status: Backlog
Development

No branches or pull requests

2 participants