[
https://issues.apache.org/jira/browse/CASSANDRA-20448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936862#comment-17936862
]
Stefan Miklosovic edited comment on CASSANDRA-20448 at 3/19/25 3:23 PM:
------------------------------------------------------------------------
The original code has this strange logic in it:
./tools/bin/sstableexpiredblockers ab cd ef gh ks tb
It will take tb as table and ks as keyspace and drops everything else.
If we introduced this
./tools/bin/sstableexpiredblockers ks tb --human-readable
Then keyspace would be "tb" and "--human-readable" would be table, no?
I think what is currently there is quite weird and I would not be afraid of
breaking it.
If only this is possible:
./tools/bin/sstableexpiredblockers --human-readable ks tb
we could do that, yeah. So instead "false / true" you want to see
"--human-readable", right?
What happens when "ks tb --human-readable" is specified? We should fail?
was (Author: smiklosovic):
The original code has this strange logic in it:
./tools/bin/sstableexpiredblockers ab cd ef gh ks tb
It will take tb as table and ks as keyspace and drops everything else.
If we introduced this
./tools/bin/sstableexpiredblockers ks tb --human-readable
Then keyspace would be "tb" and "--human-readable" would be table, no?
I think what is currently there is quite weird and I would not be afraid of
breaking it.
> Utility sstableexpiredblockers should report the size of expired tables
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-20448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20448
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Legacy/Tools
> Reporter: Brad Schoening
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A key reason to run sstableexpiredblockers is that you have disk space
> accumulating and you wish to investigate what's consuming the disk space.
> If size was included in the output (as shown below), it would make the output
> more useful. Generally, when you find a blocked expired table, the first step
> is to check what size it is to see if it's large enough to be a problem.
> {quote}[BigTableReader(path='/var/lib/cassandra/data/keyspace1/standard1-0665ae80b2d711e886c66d2c86545d91/mc-2-big-Data.db')
> (minTS = 5, maxTS = 5, maxLDT = 2147483647)], blocks 1 expired sstables from
> getting dropped:
> [BigTableReader(path='/var/lib/cassandra/data/keyspace1/standard1-0665ae80b2d711e886c66d2c86545d91/mc-3-big-Data.db')
> (\{*}diskSize = 135.7 GB\{*}, minTS = 1536349775157606, maxTS =
> 1536349780311159, maxLDT = 1536349780)],
> {quote}
> Also, it would be preferable to report min/max timestamp in date-time format
> e.g.:
> {quote} diskSize =134.3 GB, minTimestamp =
> 2025-03-10T00:00:00.000+00:00
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
