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

Ahmed Bashir edited comment on CASSANDRA-5067 at 2/5/13 1:59 AM:
-----------------------------------------------------------------

DatabaseDescriptor.java has a static init block where loadYaml() is called.  We 
could follow that with loadOverrides() to see if any of the fields in 
Config.java have overrides.  Everything in Config can be overridden, just like 
everything in Config can be loaded from a yaml file.  There's no need to reason 
about whether new fields can be overridden or not, just like we don't have to 
think about whether or not they can be specified in the yaml file.

To my knowledge, there's nothing in the yaml file that can't be specified on 
the command line in some canonical form (numbers, strings, lists, etc)

Introducing more (yaml) files is a nonstarter IMO

                
      was (Author: abashir):
    DatabaseDescriptor.java has a static init block where loadYaml() is called. 
 We could follow that with loadOverrides() to see if any of the fields in 
Config.java have overrides.  Everything in Config can be overridden, just like 
everything in Config can be loaded from a yaml file.  There's no need to reason 
about whether new fields can be overridden or not, just like we don't have to 
think about whether or not they can be specified in the yaml file.

To my knowledge, there's nothing in the yaml file that can't be specified on 
the command line in some canonical form (numbers, strings, lists, etc)

Additional more files is a nonstarter IMO

                  
> Allow basic yaml properties to be specified via JVM parameters
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-5067
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5067
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ahmed Bashir
>            Priority: Trivial
>              Labels: ponies
>
> In the case of large clusters, each node operates with a cassandra.yaml that 
> is nearly identical to every other node with the exception of some basic 
> properties:
> listen_address
> rpc_address 
> initial_token
> data_file_directories
> etc
> If it was possible to specific these as JVM parameters, we wouldn't have to 
> prepare a customized cassandra.yaml for each node but rather share a single 
> cassandra.yaml file.  This is increasingly important when the number of nodes 
> being managed gets very large. 

--
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

Reply via email to