cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-813) add some kind of logging of GC activity
Date Sat, 20 Feb 2010 16:20:27 GMT

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

Jonathan Ellis commented on CASSANDRA-813:
------------------------------------------

Looks like the only way is to redirect stdout? err? to log4j.

Juha at http://stackoverflow.com/questions/1200175/log4j-redirect-stdout-to-dailyrollingfileappender
offers:

// PrintStream object that prints stuff to log4j logger
public class Log4jStream extends PrintStream {
      public void write(byte buf[], int off, int len) {
        try {
           // write stuff to Log4J logger
        } catch (Exception e) {
       }
    }
}

// reassing standard output to go to log4j
System.setOut(new Log4jStream());


> add some kind of logging of GC activity
> ---------------------------------------
>
>                 Key: CASSANDRA-813
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-813
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 0.6
>
>
> "help, my node froze when i hammered it too hard" is a faq. before we have CASSANDRA-685
it would be nice to make it obvious what is going on w/ gc storms.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message