cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5067) Allow basic yaml properties to be specified via JVM parameters
Date Thu, 13 Dec 2012 22:46:15 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-5067:
--------------------------------------

             Priority: Trivial  (was: Major)
    Affects Version/s:     (was: 1.1.5)
               Labels: ponies  (was: )

Or you could just use a real configuration management system.
                
> 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

Mime
View raw message