cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9694) system_auth not upgraded
Date Wed, 15 Jul 2015 14:14:04 GMT

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

Sam Tunnicliffe commented on CASSANDRA-9694:
--------------------------------------------

Sorry it's taken a while to get back to you on this. I'm still not seeing any auth-related
issues here. In the latest logs, I see the initial data conversion tasks fail as expected:
{noformat}
INFO  [OptionalTasks:1] 2015-07-08 12:06:09,804 CassandraRoleManager.java:413 - Unable to
complete conversion of legacy auth data (perhaps not enough nodes are upgraded yet). Conversion
should not be considered complete
...
INFO  [OptionalTasks:1] 2015-07-08 12:06:19,814 CassandraAuthorizer.java:440 - Unable to complete
conversion of legacy permissions data (perhaps not enough nodes are upgraded yet). Conversion
should not be considered complete
{noformat}

and then no further mention of anything in the auth subsystems. There aren't any errors resembling
the ones from the issue description or the comments on 02/07.

Around the 12:16 mark where you issue some queries as an authenticated user, there are some
connection reset events, but these don't look related to either authentication or permissions.
Turning on query tracing for those requests may shed more light on what's happening there.

> system_auth not upgraded
> ------------------------
>
>                 Key: CASSANDRA-9694
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9694
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Windows-7-32 bit, 3.2GB RAM, Java 1.7.0_55
>            Reporter: Andreas Schnitzerling
>            Assignee: Sam Tunnicliffe
>             Fix For: 2.2.0
>
>         Attachments: 9694.txt, system.log.1.zip, system.log.1a.zip, system.log.2..zip,
system.log.2a.zip, system_exception.log
>
>
> After upgrading Authorization-Exceptions occur. I checked the system_auth keyspace and
have seen, that tables users, credentials and permissions were not upgraded automatically.
I upgraded them (I needed 2 times per table because of CASSANDRA-9566). After upgrading the
system_auth tables I could login via cql using different users.
> {code:title=system.log}
> WARN  [Thrift:14] 2015-07-01 11:38:57,748 CassandraAuthorizer.java:91 - CassandraAuthorizer
failed to authorize #<User updateprog> for <keyspace logdata>
> ERROR [Thrift:14] 2015-07-01 11:41:26,210 CustomTThreadPoolServer.java:223 - Error occurred
during processing of message.
> com.google.common.util.concurrent.UncheckedExecutionException: java.lang.RuntimeException:
org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - received only
0 responses.
> 	at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2201) ~[guava-16.0.jar:na]
> 	at com.google.common.cache.LocalCache.get(LocalCache.java:3934) ~[guava-16.0.jar:na]
> 	at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3938) ~[guava-16.0.jar:na]
> 	at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4821) ~[guava-16.0.jar:na]
> 	at org.apache.cassandra.auth.PermissionsCache.getPermissions(PermissionsCache.java:72)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.auth.AuthenticatedUser.getPermissions(AuthenticatedUser.java:104)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.service.ClientState.authorize(ClientState.java:362) ~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.service.ClientState.checkPermissionOnResourceChain(ClientState.java:295)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.service.ClientState.ensureHasPermission(ClientState.java:272)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.service.ClientState.hasAccess(ClientState.java:259) ~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.service.ClientState.hasColumnFamilyAccess(ClientState.java:243)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.cql3.statements.SelectStatement.checkAccess(SelectStatement.java:143)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:222)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:256) ~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:241) ~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.thrift.CassandraServer.execute_cql3_query(CassandraServer.java:1891)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4588)
~[apache-cassandra-thrift-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.cassandra.thrift.Cassandra$Processor$execute_cql3_query.getResult(Cassandra.java:4572)
~[apache-cassandra-thrift-2.2.0-rc1.jar:2.2.0-rc1]
> 	at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) ~[libthrift-0.9.2.jar:0.9.2]
> 	at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) ~[libthrift-0.9.2.jar:0.9.2]
> 	at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:204)
~[apache-cassandra-2.2.0-rc1.jar:2.2.0-rc1]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.7.0_55]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.7.0_55]
> 	at java.lang.Thread.run(Unknown Source) [na:1.7.0_55]
> {code}



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

Mime
View raw message