[ https://issues.apache.org/jira/browse/CASSANDRA-19033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Haddad updated CASSANDRA-19033: ----------------------------------- Summary: Add virtual table with GC pause history (was: Add virtual tables with GC pause history) > Add virtual table with GC pause history > --------------------------------------- > > Key: CASSANDRA-19033 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19033 > Project: Cassandra > Issue Type: New Feature > Components: Feature/Virtual Tables > Reporter: Jon Haddad > Priority: Normal > > We should be able to view GC pause history in a virtual table. > I think the best approach here is to read from the GC logs. The format was > unified in Java 9, and we've dropped older JVM support so I think this is > reasonable. The benefits of using logs are that we can preserve it across > restarts and we enable GC logs by default. > The downside is people might not have GC logs configured and it seems weird > that a feature would just stop working because logs aren't enabled. Maybe > that's OK if we call it out, or error if people try to read from it and the > logs aren't enabled. I think if someone disables -Xlog:gc then an error > might be fine as I don't expect it to happen often. I think I lean towards > this from a usability perspective, and Microsoft has a > [project|https://github.com/microsoft/gctoolkit] to parse them, but I haven't > used it so I'm not sure if it's suitable for us. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org