cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5049) Auth.setup() is called too early
Date Mon, 10 Dec 2012 19:41:21 GMT

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

Aleksey Yeschenko commented on CASSANDRA-5049:
----------------------------------------------

Committed, thanks.
                
> Auth.setup() is called too early
> --------------------------------
>
>                 Key: CASSANDRA-5049
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5049
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.0 rc1
>
>         Attachments: 5049.txt, 5049-v2.txt
>
>
> Auth.setup() triggers a request against the system_auth keyspace, request that is not
an internal one, so it at least require TokenMetadata to be set up. However, Auth.setup()
is call much too early, even before the commit log is replayed. The only reason this doesn't
trigger an assertionError everytime is because Auth.setup() actually only schedul it's request
after RING_DELAY, but still, replaying the commit log can take much more than that, and even
without that I suspect this would be racy with normal bootstrap.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message