[
https://issues.apache.org/jira/browse/CASSANDRA-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613361#comment-17613361
]
Michiel Saelen commented on CASSANDRA-17948:
--------------------------------------------
Hi [~smiklosovic],
Indeed for our use case, it would be beneficial if you could expose the
partitions that crossed the thresholds directly into a virtual table (or have
Cassandra protect itself).
Blocking further inserts on Cassandra's side sounds like a good improvement to
ensure more stability. To give you an example, we noticed Cassandra was
struggling during compaction and then noticed we had created a partition of
50G. If the query would fail in this case, would it be possible to tell it is
because of the partition size?
Next to this, I still believe that making logs available through virtual tables
would also be a great feature.
Thanks for your input on this
> 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]
