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

Active tablet counts by AZ are incorrect in master ui #1428

Closed
srhickma opened this issue May 23, 2019 · 0 comments
Closed

Active tablet counts by AZ are incorrect in master ui #1428

srhickma opened this issue May 23, 2019 · 0 comments
Assignees
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug

Comments

@srhickma
Copy link
Contributor

Currently the "Total Tablet-Peers" counts in the "Tablet-Peers by Availability Zone" table lists the total number of tablet peers, not the total number of active tablet peers.

@srhickma srhickma added kind/bug This issue is a bug area/docdb YugabyteDB core features labels May 23, 2019
@srhickma srhickma self-assigned this May 23, 2019
yugabyte-ci pushed a commit that referenced this issue May 24, 2019
Summary:
Renamed the last columns in both tables in the master tablets ui to include the word
"Active", and fixed the last column in the "Tablet-Peers by Availability Zone" table to only include
active tablet-peers (rather than active and inactive).

Caused by 29a4a8a

Test Plan:
Manually tested by starting a local cluster, adding nodes and tables, then verifying that the table shows the correct values. Ran `CassandraKeyValue` workload for several minutes, then restarted a node, the following screenshot shows the tablets page a few seconds after the restart. The "Total Active Tablet-Peers" column is now the correct sum.

{F12219}

Reviewers: kannan, bogdan

Reviewed By: kannan, bogdan

Subscribers: kannan, ybase, bogdan

Differential Revision: https://phabricator.dev.yugabyte.com/D6664
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug
Projects
None yet
Development

No branches or pull requests

1 participant