Why not change the option so that -H will operate as it does now while -Hn
(where n is a digit) will limit the number of decimal places to n.
On Mon, Dec 4, 2023 at 5:11 PM Brad wrote:
> Thanks, Jacek. Using three significant digits for disk space is a good
> suggestion.
>
> On Mon, Dec 4, 2023
Thanks, Jacek. Using three significant digits for disk space is a good
suggestion.
On Mon, Dec 4, 2023 at 9:58 AM Jacek Lewandowski <
lewandowski.ja...@gmail.com> wrote:
> This looks great,
>
> I'd consider limiting the number of significant digits to 3 in the human
> readable format. In the abo
This looks great,
I'd consider limiting the number of significant digits to 3 in the human
readable format. In the above example it would translate to:
Space used (live): 1.46 TiB
Space used (total): 1.46 TiB
Bytes repaired: 0.00 KiB
Bytes unrepaired: 4.31 TiB
Bytes pending repair: 0.000 KiB
I
Given how fundamental disk space is to operational competence, it's
hard to imagine anyone actually parsing this output instead of using
at least something like the machine readable option. The switch is
rather simple if they need to make it, and they will be better for it,
so I support tidying up
Tablestats currently reports output in a mixed format which is neither
ideal for human readability nor machine readability. Spaces are also
inconsistently used and 13 digit numbers w/out commas or larger units are
complicated to read.
For example, 'Bytes repaired / un-repaired / pending' uses KiB
+1
Kind Regards,
Brandon
On Fri, Dec 1, 2023 at 7:32 AM Mick Semb Wever wrote:
>
>
> Proposing the test build of Cassandra 5.0-beta1 for release.
>
> sha1: 87fd1fa88a0c859cc32d9f569ad09ad0b345e465
> Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative
> Maven Artifacts:
> https://r
Thanks for the feedback. To wrap this up we will introduce a new SAI local
read metric (name to be decided later) to record read count and latency and
these reads to be kept separate from existing local range read metrics.
On Fri, 1 Dec 2023 at 19:10, Jeremiah Jordan
wrote:
> Again I am coming a
