[jira] [Commented] (CASSANDRA-9124) GCInspector logs very different times after CASSANDRA-7638
[
https://issues.apache.org/jira/browse/CASSANDRA-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14515991#comment-14515991
]
Charles Cao commented on CASSANDRA-9124:
any update? Can somebody review and commit the fix?
GCInspector logs very different times after CASSANDRA-7638
--
Key: CASSANDRA-9124
URL: https://issues.apache.org/jira/browse/CASSANDRA-9124
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Jeremiah Jordan
Assignee: Ariel Weisberg
Priority: Minor
Fix For: 3.0, 2.1.5
After the GCInspector rewrite in CASSANDRA-7638 the times reported for CMS
are the full time (including all the concurrent time), not just the stop the
world pause time. In previous versions we reported just the stop the world
pause time. This change is kind of scary for someone used to the old logs,
and is also not as useful. You can't get how long were things really
stopped from the log message any more.
For example, this is a CMS that got logged in C* 2.1:
{noformat}
INFO [Service Thread] 2015-04-03 23:58:37,583 GCInspector.java:142 -
ConcurrentMarkSweep GC in 12926ms. CMS Old Gen: 5305346280 - 1106799064;
Par Eden Space: 223080 - 158423560; Par Survivor Space: 42081744 - 51339584
{noformat}
And here is the corresponding information for that CMS from the gc log.
{noformat}
2015-04-03T23:58:24.656+: 8064.780: [GC [1 CMS-initial-mark:
5181002K(6901760K)] 5222315K(7639040K), 0.0316710 secs] [Times: user=0.03
sys=0.00, real=0.03 secs]
2015-04-03T23:58:24.688+: 8064.812: Total time for which application
threads were stopped: 0.0324490 seconds
2015-04-03T23:58:24.688+: 8064.812: [CMS-concurrent-mark-start]
2015-04-03T23:58:26.939+: 8067.062: [CMS-concurrent-mark: 2.176/2.250
secs] [Times: user=12.94 sys=1.73, real=2.25 secs]
2015-04-03T23:58:26.939+: 8067.063: [CMS-concurrent-preclean-start]
2015-04-03T23:58:27.209+: 8067.333: [CMS-concurrent-preclean: 0.187/0.270
secs] [Times: user=1.53 sys=0.15, real=0.28 secs]
2015-04-03T23:58:27.210+: 8067.333:
[CMS-concurrent-abortable-preclean-start]
2015-04-03T23:58:27.988+: 8068.112: [CMS-concurrent-abortable-preclean:
0.759/0.779 secs] [Times: user=4.07 sys=0.74, real=0.77 secs]
2015-04-03T23:58:27.989+: 8068.113: [GC[YG occupancy: 488441 K (737280
K)]2015-04-03T23:58:27.989+: 8068.113: [Rescan (parallel) , 0.3688960
secs]2015-04-03T23:58:28.358+: 8068.482: [weak refs processing, 0.0009620
secs]2015-04-03T23:58:28.359+: 8068.483: [class unloading, 0.0060870
secs]2015-04-03T23:58:28.365+: 8068.489: [scrub symbol table, 0.0146010
secs]2015-04-03T23:58:28.380+: 8068.504: [scrub string table, 0.0031270
secs] [1 CMS-remark: 5231445K(6901760K)] 5719886K(7639040K), 0.3953770 secs]
[Times: user=2.96 sys=0.00, real=0.39 secs]
2015-04-03T23:58:28.385+: 8068.508: Total time for which application
threads were stopped: 0.3962470 seconds
2015-04-03T23:58:28.385+: 8068.509: [CMS-concurrent-sweep-start]
2015-04-03T23:58:37.582+: 8077.706: [CMS-concurrent-sweep: 8.661/9.197
secs] [Times: user=44.80 sys=9.58, real=9.20 secs]
2015-04-03T23:58:37.589+: 8077.713: [CMS-concurrent-reset-start]
2015-04-03T23:58:37.633+: 8077.757: [CMS-concurrent-reset: 0.044/0.044
secs] [Times: user=0.19 sys=0.10, real=0.04 secs]
{noformat}
The entire CMS took the 12 seconds reported in the GCIspector log message.
Previously we would have only reported the 0.39 seconds that were spent in
STW pauses.
At the least we need to change the log message so that people don't think we
are still just reporting STW time. But it would be more helpful if we could
get the STW time and put that into the log message like we had previously.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-7899) SSL does not work in cassandra-cli
[ https://issues.apache.org/jira/browse/CASSANDRA-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14169587#comment-14169587 ] Charles Cao commented on CASSANDRA-7899: What is the fix version? SSL does not work in cassandra-cli -- Key: CASSANDRA-7899 URL: https://issues.apache.org/jira/browse/CASSANDRA-7899 Project: Cassandra Issue Type: Bug Components: Tools Environment: Linux 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 21:14:45 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux java version 1.7.0_17 Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) [cqlsh 4.1.1 | Cassandra 2.0.10 | CQL spec 3.1.1 | Thrift protocol 19.39.0] Reporter: Zdenek Ott Assignee: Jason Brown Attachments: 7899-v1.txt, 7899-v2.txt When specify transport factory parameter '-tf org.apache.cassandra.cli.transport.SSLTransportFactory' it throws exception, see below, because SSLTransportFactory extends TTransportFactory not ITransportFactory. Exception in thread main java.lang.IllegalArgumentException: Cannot create a transport factory 'org.apache.cassandra.cli.transport.SSLTransportFactory'. at org.apache.cassandra.cli.CliOptions.validateAndSetTransportFactory(CliOptions.java:288) at org.apache.cassandra.cli.CliOptions.processArgs(CliOptions.java:223) at org.apache.cassandra.cli.CliMain.main(CliMain.java:230) Caused by: java.lang.IllegalArgumentException: transport factory 'org.apache.cassandra.cli.transport.SSLTransportFactory' not derived from ITransportFactory at org.apache.cassandra.cli.CliOptions.validateAndSetTransportFactory(CliOptions.java:282) ... 2 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-6904) commitlog segments may not be archived after restart
[ https://issues.apache.org/jira/browse/CASSANDRA-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14152144#comment-14152144 ] Charles Cao commented on CASSANDRA-6904: Is there anybody reviewing the patch now? commitlog segments may not be archived after restart Key: CASSANDRA-6904 URL: https://issues.apache.org/jira/browse/CASSANDRA-6904 Project: Cassandra Issue Type: Bug Components: Core Reporter: Jonathan Ellis Assignee: Sam Tunnicliffe Fix For: 2.0.11, 2.1.1 Attachments: 2.0-6904.txt, 2.1-6904-v2.txt, 2.1-6904.txt commitlog segments are archived when they are full, so the current active segment will not be archived on restart (and its contents will not be available for pitr). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CASSANDRA-7028) Allow C* to compile under java 8
[ https://issues.apache.org/jira/browse/CASSANDRA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14134079#comment-14134079 ] Charles Cao commented on CASSANDRA-7028: Can we also compile and run C* 2.0.x under JDK 8? Allow C* to compile under java 8 Key: CASSANDRA-7028 URL: https://issues.apache.org/jira/browse/CASSANDRA-7028 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Dave Brosius Assignee: Aleksey Yeschenko Priority: Minor Fix For: 2.1.1, 3.0 Attachments: 7028.txt, 7028_v2.txt, 7028_v3.txt, 7028_v4.txt, 7028_v5.patch antlr 3.2 has a problem with java 8, as described here: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8015656 updating to antlr 3.5.2 solves this, however they have split up the jars differently, which adds some changes, but also the generation of CqlParser.java causes a method to be too large, so i needed to split that method to reduce the size of it. (patch against trunk) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
