cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Yudovin (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12624) Add cassandra.yaml overlay capabilities (can issue pull request now)
Date Fri, 02 Dec 2016 14:16:58 GMT


Vladimir Yudovin commented on CASSANDRA-12624:

Hi Craig,

there are some fields that contradict one to another and can't be used simultaneously, e.g.
listen_address and listen_interface. If one of them is set in main file and other in overlay
Cassandra start will fail. Such exclusion should be handled individually.

Also I used simpler approach for  CASSANDRA-12970, simple concatenation of YAML file in memory.
Thus new values overrides old ones. May be we can combine our solutions in some way.

> Add cassandra.yaml overlay capabilities (can issue pull request now)
> --------------------------------------------------------------------
>                 Key: CASSANDRA-12624
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>         Environment: OSX but should work on any OS.
>            Reporter: Craig McConomy
>            Priority: Minor
>              Labels: configuration, configuration-addition
>             Fix For: 3.x
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> Adds a new file "conf/cassandra-overlay.yaml" that can contain any settings found in
cassandra.yaml. Any settings, if found, override whatever is found in cassandra.yaml
> A different overlay file can be specified using -Dcassandra.config.overlay=your_file_name
> Overlay processing can be disabled with -Dcassandra.config.overlay.disable=true
> Rationale: When administering cassandra nodes, I have found it quite common to want to
distribute a common "golden" cassandra.yaml. This is challenging where you have a configuration
value or two that needs to be modified per node. In this case, ops needs to know which lines
of cassandra.yaml to ignore (because it's the same on all nodes) so that they can focus on
what's uniquely configured for a particular node.
> By specifying an additional overlay file, cassandra admins have the flexibility to decide
what is configured on a per-node basis, and can make it extremely clear.
> Source can be found in

This message was sent by Atlassian JIRA

View raw message