[
https://issues.apache.org/jira/browse/CASSANDRA-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734527#comment-14734527
]
Sam Tunnicliffe edited comment on CASSANDRA-10209 at 9/8/15 10:04 AM:
----------------------------------------------------------------------
Committed with [~carlyeks]'s additions as
{{0c0f1ff1b1051627f38a8bf6cb0776241586dfce}}.
I notice that since the revert, {{UFTest.testTypesWithAndWithoutNulls}} has
been failing with a timeout. This is doubly weird given it was just a revert,
plus the same test is fine on 3.0 & trunk. I've also run being running
{{UFTest}} in a loop locally and seen no errors in 65 runs.
[~mshuler], any ideas about the above? Also, another oddity is that
{{CQLSSTableWriterClientTest}} (where the offending test from 2.2 was moved to)
never failed on 3.0 or trunk, even before the revert. I would have expected 3.0
to have hit the same NPE from [this
build|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_testall/90/],
and indeed running the test locally with that revision fails in exactly the
expected way.
was (Author: beobal):
Committed with [~carlyeks]'s additions as
{{0c0f1ff1b1051627f38a8bf6cb0776241586dfce}}.
I notice that since the revert, {{UFTest.testTypesWithAndWithoutNulls}} has
been failing with a timeout. This is doubly weird given it was just a revert,
plus the same test is fine on 3.0 & trunk. I've also run being running
{{UFTest}} in a loop locally and seen no errors in 65 runs.
[~mshuler], any ideas about the above? Also, another oddity is that
{{CQLSSTableWriterClientTest}} (where the offending test from 2.2 was moved to)
never failed on 3.0 or trunk, even before the revert. I would have expected 3.0
to have hit the same NPE from [this
build|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_testall/90/],
and indeed running the test locally with that revision fails in exactly the
unexpected way.
> Missing role manager in cassandra.yaml causes unexpected behaviour
> ------------------------------------------------------------------
>
> Key: CASSANDRA-10209
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10209
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Fix For: 3.0.0 rc1, 2.2.2
>
>
> On upgrading to 2.2+, if the new {{role_manager}} option is not added to
> {{cassandra.yaml}}, an instance of the default {{CassandraRoleManager}} is
> created during initialization of {{DatabaseDescriptor}}. This is a problem as
> the set of role options supported by {{CRM}} depends on the configured
> {{IAuthenticator}}, which at that point in time is always
> {{AllowAllAuthenticator}}.
> This StackOverflow post describes the problem; the configured authenticator
> is {{PasswordAuthenticator}}, the role manager should allow roles to be
> created using the {{PASSWORD}} option, but it does not.
> http://stackoverflow.com/questions/31820914/in-cassandra-2-2-unable-to-create-role-containing-password
> The simple workaround is to ensure that yaml contains the role manager option
> {code}
> role_manager: CassandraRoleManager
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
