[ https://issues.apache.org/jira/browse/CASSANDRA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Olsson updated CASSANDRA-8376: ------------------------------------- Attachment: cassandra-2.1-8376.patch Unfortunately I seem to be unable to assign myself to the ticket, is that a separate permission you need? The attached patch is an extension to the current YamlConfigurationLoader using a conf.d directory that is scanned at startup and overrides configuration from cassandra.yaml. The files in the conf.d directory are read in order based on their names. > Add support for multiple configuration files (or conf.d) > -------------------------------------------------------- > > Key: CASSANDRA-8376 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8376 > Project: Cassandra > Issue Type: New Feature > Reporter: Omri Bahumi > Attachments: cassandra-2.1-8376.patch > > > I'm using Chef to generate cassandra.yaml. > Part of this file is the "seed_provider", which is based on the Chef > inventory. > Changes to this file (due to Chef inventory change, when adding/removing > Cassandra nodes) cause a restart, which is not desirable. > The Chef way of handling this is to split the config file into two config > files, one containing only the "seed_provider" and the other containing the > rest of the config. > Only the latter will cause a restart to Cassandra. > This is achievable by either: > 1. Specifying multiple config files to Cassandra > 2. Specifying a conf.d directory -- This message was sent by Atlassian JIRA (v6.3.4#6332)