[
https://issues.apache.org/jira/browse/CASSANDRA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224743#comment-15224743
]
Aleksey Yeschenko commented on CASSANDRA-8376:
----------------------------------------------
As my past self noted all the way in 2014, you can accomplish that with
CASSANDRA-5045 - with a custom implementation of the config loader. It doesn't
need to be in C* core, and that's in fact the whole reason for making it
pluggable in the first place.
Closing as Not A Problem, with CASSANDRA-5045 linked.
> 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)
