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

FE: Fix 'Online Partitions' column #607

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

bachmanity1
Copy link
Contributor

@bachmanity1 bachmanity1 commented Oct 13, 2024

  • Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Resolves #526.

The value shown in the Online Partitions column of the brokers list table was modified in #137. This PR restores the original logic used to render Online Partitions prior to #137.

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

  • No need to
  • Manually (please, describe, if necessary)
  • Unit checks
  • Integration checks
  • Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
  • My changes generate no new warnings (e.g. Sonar is happy)
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

@bachmanity1 bachmanity1 requested a review from a team as a code owner October 13, 2024 09:32
@kapybro kapybro bot added status/triage Issues pending maintainers triage status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Oct 13, 2024
@Haarolean
Copy link
Member

Haarolean commented Oct 16, 2024

This PR restores the original logic

@bachmanity1 hi, could you please elaborate here? The changes previously introduced were done so with a purpose (even if introducing incorrect behavior), so reverting these changes you're probably introducing another faulty behavior that was present before #137 (#26)?

Copy link

kapybro bot commented Oct 16, 2024

Further user feedback is requested. Please reply within 7 days or we might close the issue.

@bachmanity1
Copy link
Contributor Author

bachmanity1 commented Oct 17, 2024

This PR restores the original logic

@bachmanity1 hi, could you please elaborate here? The changes previously introduced were done so with a purpose (even if introducing incorrect behavior), so reverting these changes you're probably introducing another faulty behavior that was present before #137 (#26)?

Hi @Haarolean, thanks for review!

You're right. We can't simply revert the changes made in #137 because that would bring back the original faulty behavior. While the changes in #137 fixed the issue with the Online Partitions column's color, they also caused every row in the brokers table to show the same value in that column. From looking at the backend code, it seems that Online Partitions refers to partitions where the describeTopics API doesn't return null for the partition leader. While it's possible to compute this for the whole cluster, I don't think it's possible (or needed?) to do so for each individual broker.

So, how about renaming the Online Partitions column to just Partitions and showing the actual number of partitions (replicas) located on each broker by using partitions field from the broker info? If possible, I'd even suggest renaming Online Partitions to Replicas and Partitions Skew to Replicas Skew. I think this would make more sense, since in Kafka terminology, partitions stored on brokers are referred to as replicas.

Copy link

kapybro bot commented Oct 17, 2024

Thanks for the additional feedback! We'll get back to your issue soon.

@Haarolean Haarolean added the hacktoberfest-accepted PRs accepted towards hacktoberfest goal and will be counted as approved label Oct 22, 2024
@Haarolean Haarolean self-requested a review October 22, 2024 17:50
@bachmanity1
Copy link
Contributor Author

bachmanity1 commented Oct 25, 2024

Hi @Haarolean,

Following my last comment, I've made slight changes to the brokers table by rearranging the order and renaming columns. Here is a sample screenshot:

image

@bachmanity1
Copy link
Contributor Author

Hi @Haarolean, can you have a look at this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest-accepted PRs accepted towards hacktoberfest goal and will be counted as approved scope/frontend Related to frontend changes status/triage/completed Automatic triage completed status/triage/manual Manual triage in progress
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Brokers: Wrong 'Online partition count' value
2 participants