You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Wei Deng (JIRA)" <ji...@apache.org> on 2016/08/20 22:04:20 UTC

[jira] [Created] (CASSANDRA-12512) compaction-stress: assertion error on accessing Schema.instance from client-mode tool

Wei Deng created CASSANDRA-12512:
------------------------------------

             Summary: compaction-stress: assertion error on accessing Schema.instance from client-mode tool
                 Key: CASSANDRA-12512
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12512
             Project: Cassandra
          Issue Type: Bug
            Reporter: Wei Deng


When I was trying the new compaction-stress tool from 3.10, I ran into the following error:

{noformat}
automaton@wdengsummitsparkgoogle-0ce59d338-1:~/cassandra-trunk$ ./tools/bin/compaction-stress write -d /tmp/compaction -g 5 -p https://gist.githubusercontent.com/tjake/8995058fed11d9921e31/raw/a9334d1090017bf546d003e271747351a40692ea/blogpost.yaml -t 4
java.lang.AssertionError: This assertion failure is probably due to accessing Schema.instance from client-mode tools - See CASSANDRA-8143.
	at org.apache.cassandra.config.CFMetaData.<init>(CFMetaData.java:288)
	at org.apache.cassandra.config.CFMetaData.<init>(CFMetaData.java:66)
	at org.apache.cassandra.config.CFMetaData$Builder.build(CFMetaData.java:1332)
	at org.apache.cassandra.config.CFMetaData.compile(CFMetaData.java:433)
	at org.apache.cassandra.stress.StressProfile.init(StressProfile.java:174)
	at org.apache.cassandra.stress.StressProfile.load(StressProfile.java:801)
	at org.apache.cassandra.stress.CompactionStress.getStressProfile(CompactionStress.java:162)
	at org.apache.cassandra.stress.CompactionStress$DataWriter.run(CompactionStress.java:289)
	at org.apache.cassandra.stress.CompactionStress.main(CompactionStress.java:353)
{noformat}

Probably another code path not covered by CASSANDRA-8143? From the [comment|https://issues.apache.org/jira/browse/CASSANDRA-8143?focusedCommentId=14802787&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14802787] it appears that this should no longer happen after the patch and I confirmed the patch is in the code I'm using.



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