[
https://issues.apache.org/jira/browse/CASSANDRA-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176249#comment-13176249
]
Peter Schuller commented on CASSANDRA-3674:
-------------------------------------------
It prints the heap usage after trying to obtain it "as soon as possible" after
the explicit GC completes.
I did however just realize that I haven't tested whether the explicit gc
invocation is blocking in the case of -XX:+ExplicitGCInvokesConcurrent.
> add nodetool explicitgc
> -----------------------
>
> Key: CASSANDRA-3674
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3674
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Peter Schuller
> Assignee: Peter Schuller
> Priority: Minor
> Attachments: CASSANDRA-3674-trunk.txt
>
>
> So that you can easily ask people "run nodetool explicitgc and paste the
> results".
> I'll file a separate JIRA suggesting that we ship with
> -XX:+ExplicitGCInvokesConcurrent by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
