cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-9020) java.lang.AssertionError on node startup
Date Mon, 23 Mar 2015 17:45:11 GMT
Philip Thompson created CASSANDRA-9020:

             Summary: java.lang.AssertionError on node startup
                 Key: CASSANDRA-9020
             Project: Cassandra
          Issue Type: Bug
            Reporter: Philip Thompson
            Assignee: Sam Tunnicliffe
             Fix For: 3.0
         Attachments: node1.log, node2.log, node3.log

Occasionally when running dtests, I will see this exception when starting a test:
ERROR [main] 2015-03-23 13:23:25,719 - Exception encountered during
java.lang.AssertionError: org.apache.cassandra.exceptions.InvalidRequestException: unconfigured
table roles
        at org.apache.cassandra.auth.CassandraRoleManager.prepare(
        at org.apache.cassandra.auth.CassandraRoleManager.setup(
        at org.apache.cassandra.service.StorageService.doAuthSetup(
        at org.apache.cassandra.service.StorageService.joinTokenRing(
        at org.apache.cassandra.service.StorageService.initServer(
        at org.apache.cassandra.service.StorageService.initServer(
        at org.apache.cassandra.service.CassandraDaemon.setup( [main/:na]
        at org.apache.cassandra.service.CassandraDaemon.activate(
        at org.apache.cassandra.service.CassandraDaemon.main( [main/:na]
Caused by: org.apache.cassandra.exceptions.InvalidRequestException: unconfigured table roles
        at org.apache.cassandra.thrift.ThriftValidation.validateColumnFamily(
        at org.apache.cassandra.cql3.statements.SelectStatement$RawStatement.prepare(
        at org.apache.cassandra.auth.CassandraRoleManager.prepare(
        ... 8 common frames omitted

Most recently it occurred on {{test_paging_across_multi_wide_rows (paging_test.TestPagingData)}},
though I have seen it in other tests. It does not reproduce consistently. I have attached
the system.log file of an affected node, node1.log.   The other two log files belong to other
nodes in the cluster, in case that helps.

This message was sent by Atlassian JIRA

View raw message