[
https://issues.apache.org/jira/browse/CASSANDRA-19801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876100#comment-17876100
]
Brad Schoening edited comment on CASSANDRA-19801 at 8/22/24 8:38 PM:
---------------------------------------------------------------------
[[email protected]] we looked into humongous allocations in
CASSANDRA-17655 and couldn't find a MBean or other way to determine region size
programmatically.
was (Author: bschoeni):
[[email protected]] we looked into humongous allocations in
CASSANDRA-17655 and couldn't find a MBean or other way to determine region size.
> Ability to log large objects with query that's reading it
> ---------------------------------------------------------
>
> Key: CASSANDRA-19801
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19801
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Steve Lacerda
> Priority: Urgent
>
> We often encounter cases where humongous object allocations cause long GC
> pauses. However, identifying the cause is very difficult because you must use
> a profiler to catch the allocations before GC.
> It would be nice to add a TRACE-level logger to the ReadCommand or
> ReadExecutor classes. This would allow us to turn on code that calculates the
> cell size and, if it exceeds the heap region size (which varies by heap
> size), triggers a message in the logs that identifies the query that
> triggered the large read with the partition key and query parameters so it's
> easy to ID the cell.
> It might be easier to log on the write rather than the read path.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
