cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10140) Enable GC logging by default
Date Mon, 24 Aug 2015 16:35:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709576#comment-14709576
] 

Ariel Weisberg commented on CASSANDRA-10140:
--------------------------------------------

OK, +1.

I asked around and it can block the VM, but I don't think it's the high pole in the tent right
now. Things are already going to be going pretty poorly in the scenarios where the VM would
block.

It also easy to disable. I know for support being able to get the GC logs for an event that
already occurred is a blessing which is why by default is > as an option.

> Enable GC logging by default
> ----------------------------
>
>                 Key: CASSANDRA-10140
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10140
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>         Attachments: CASSANDRA-10140.txt
>
>
> Overhead for the gc logging is very small (with cycling logs in 7+) and it provides a
ton of useful information. This will open up more for C* diagnostic tools to provide feedback
as well without requiring restarts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message