[
https://issues.apache.org/jira/browse/CASSANDRA-19801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lacerda updated CASSANDRA-19801:
--------------------------------------
Priority: Urgent (was: Normal)
> 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 massive object allocations cause long GC
> pauses. However, identifying the cause is very difficult because you have to
> use a profile and catch the allocations before they GC.
> It would be nice to add a TRACE level logger to the ReadCommand or
> ReadExecutor classes that would allow us to turn on code that would calculate
> the cell size and if over the heap region size (varies by heap size), trigger
> a message in the logs that identifies the query that triggered the large read
> with the partition key and query params so it's easy to ID the cell.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
