[
https://issues.apache.org/jira/browse/CASSANDRA-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613277#comment-17613277
]
Michiel Saelen commented on CASSANDRA-17948:
--------------------------------------------
[~smiklosovic], the main reason why we would like to see this implemented is
that it would allow us to identify which partitions are the large ones.
Currently, we can only know that there is a large partition through virtual
tables, but we don't know which ones are large. If we want to investigate which
ones are large we need to go through the logs (or analyze the SSTables) and
take action. We would prefer if can make our data insertion smarter, so we
block data from being inserted that is contributing to the large partitions
that are getting too large as a protection mechanism. As our request is very
specific, we made it more generic to make it more interesting for everyone.
I like the idea of [~rustyrazorblade], but would also make it configurable to
set how much MB you want to keep in memory, this way you could speed things up
if you ask for example every time the last 5 min of logs.
> Get warning and errors through virtual tables
> ---------------------------------------------
>
> Key: CASSANDRA-17948
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17948
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Michiel Saelen
> Priority: Normal
>
> The warnings and errors are currently only accessible through Cassandra logs.
> Automating the monitoring of the nodes would be much easier/secure if we can
> make use of virtual tables to get the logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
