redpanda-data
Update Console topic UI to indicate that retention.bytes is per-partition, not per topic
We seem to get questions on a frequent enough basis about the disparity between retention.bytes as configured and the total size of a topic as viewed in Console. Can we get the UI annotated to indicate that retention.bytes is the per-partition retention and not the overall topic bytes retention?
I know I've fielded this a few times for customers, and Josh Purcell had one today.
Red arrow is where I'm talking about. The disparity between the 10GB retention.bytes value that applies to the individual partition and the 134GB actual topic content size is what causes confusion.
Under the configurations tab each config is explained (there's a help tooltip for each config that explains it in more detail). There are more catches with retention enforcement such as knowing about active/inactive segments etc. So not sure what we need to do more than this, but I'll leave it to @mo-redpanda & @ivpanda
If we field this question frequently enough, it means that customers probably aren't seeing that explanation. Would it help to do any of the following:
- Add a tooltip indicating this is per partition
- Show the actual retention.bytes (e.g. if there are 3 partitions, show 30GB)?
@hcoyote what do you think? What information do users actually need from this?
Show the actual retention.bytes (e.g. if there are 3 partitions, show 30GB)?
This is not a good idea, since the majority probably knows that all such configs (segment.bytes, retention.bytes etc) are applied per partition and not per topic this would confuse the majority that understood and did not complain about this setting.
Add a tooltip indicating this is per partition
Personally I'm not a fan of tooltips if it's possibly to avoid them. So wondering if we can just fix it by showing a per partition hint. I suggested the following as part of the message viewer improvements, what do you think?
I've move this to "Queued next" until I get a confirmation on how to proceed with this one cc @ivpanda
@jvorcak This was already done, see this screenshot from latest master. I'll close this issue: