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

Kurt Greaves commented on CASSANDRA-13701:
------------------------------------------

Obviously the bug Jeff mentioned, but also we probably need to do some work on 
making configuration a bit more straightforward, as just enforcing it will make 
startup of a new cluster slightly more complicated.

At the moment you won't be able to start a node if the keyspace you specify 
doesn't exist. This is a kind of chicken and egg problem for seed nodes, which 
I believe is currently solved by seed nodes using random allocation, at which 
point you can create the keyspace and add the keyspace to the yaml for any new 
nodes.

Honestly this is probably a little bit convoluted for new users. DSE has 
obviously realised this as they have changed their yaml property to actually 
specify the RF, rather than the keyspace, which means you can specify this 
before creating the keyspace. Kind of works but not sure if it's the best 
choice.

IMO we'll need to come up with some novel way so that you can have it so you 
can configure and start a multi node cluster in a straightforward manner. I'd 
say it's reasonable that all nodes should be able to have the same underlying 
configuration, i.e, the minimum set of yaml properties is the same for all 
nodes. This would make config management for clusters much simpler rather than 
having to be aware of this, and special case seed nodes.

> Lower default num_tokens
> ------------------------
>
>                 Key: CASSANDRA-13701
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13701
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>
> For reasons highlighted in CASSANDRA-7032, the high number of vnodes is not 
> necessary. It is very expensive for operations processes and scanning. Its 
> come up a lot and its pretty standard and known now to always reduce the 
> num_tokens within the community. We should just lower the defaults.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to