[
https://issues.apache.org/jira/browse/CASSANDRA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386312#comment-16386312
]
Oleksandr Shulgin commented on CASSANDRA-5836:
----------------------------------------------
{quote}Don't assume that a new cluster is empty or that it's safe to assume
that the first ever seed node has no data. If authentication is enabled, a
default user is created. It would be very surprising for users ("can't login
with cassandra anymore!") and actually a real security issue, if that user is
recreated (if it was dropped) or the password changed back to the
default.{quote}
I indeed remember myself seeing the default superuser created again due to a
node restart on a cluster where it was dropped before that, but I'm not sure I
fully understand the mechanism. I might have forgotten some important detail,
but I think it was related to setting up a secondary DC. Unfortunately, I
don't think it was trivially reproducible. [~snazy], do you have more details
about this issue?
> Seed nodes should be able to bootstrap without manual intervention
> ------------------------------------------------------------------
>
> Key: CASSANDRA-5836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5836
> Project: Cassandra
> Issue Type: Bug
> Reporter: Bill Hathaway
> Priority: Minor
>
> The current logic doesn't allow a seed node to be bootstrapped. If a user
> wants to bootstrap a node configured as a seed (for example to replace a seed
> node via replace_token), they first need to remove the node's own IP from the
> seed list, and then start the bootstrap process. This seems like an
> unnecessary step since a node never uses itself as a seed.
> I think it would be a better experience if the logic was changed to allow a
> seed node to bootstrap without manual intervention when there are other seed
> nodes up in a ring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
