PG status widget reports wrong number of PGs peering
PG status appears to be showing the "replica count * n_peering" number, which I only noticed because the correct number is shown nearby in the health widget (screenshot attached). This is similar to the problem that existed before in the overall PG count that was fixed by using the number from the health counters instead.
Simple quick fix would be to remove this text from the pg status widget, leaving the correct text in the health widget.
#2 Updated by Yan-Fa Li over 7 years ago
OK, I looked at this a bit more closely and using the same source as the health widget wouldn't be very reliable since it's a free form text field. I think another possible solution is to simply remove the number and report without the count, since it also includes replica's. This is probably going to become even more confusing once we have erasure encoding so maybe the time is right to remove the count from this particular view.
Another possibility is for us to add an API which returns accurate PG counts for the entire cluster without replicas which I could index into using the reporting PG key with the inflated counts to display some accurate info.
#4 Updated by Christina Meno over 7 years ago
- Assignee changed from Yan-Fa Li to Neil Levine
We need a call here what to do with the 548 peering label when more than one state exists. Do we delay for more accurate information or remove this label?
Recommendation remove number and replace it with "PGs".