Thanks Michael, I'll try that then. I need to figure out how to do it with Ubuntu's upstart because I've not done it before. On 7 Jan 2016 4:25 pm, "Michael Shuler" <mich...@pbandjelly.org> wrote:
> On 01/07/2016 07:52 AM, Vasileios Vlachos wrote: > > Hello, > > > > My problem is described CASSANDRA-10872 > > <https://issues.apache.org/jira/browse/CASSANDRA-10872>. I upgraded a > > second node on the same cluster in case there was something special with > > the first node but I experienced identical behaviour. Both > > cassandra-env.sh and cassandra-rackdc.properties were replaced > > causing the node to come up in the default data centre DC1. > > > > What is the best way to upgrade to 2.0.17 in a safe manner in this case? > > How do we work around this? > > I've made a bit of headway on this, but don't have this automated in CI > fully, yet. In quick tests, I get prompted on upgrade when my config > files have changed from the originals, similar to your later comment on > that JIRA. This replacement without prompt could be a system > configuration to not prompt you(?). I'm not sure how one would change > that behavior system-wide, since I've never turned this knob, but I'd > suggest looking at debconf options. > > I'm in favor of CASSANDRA-2356, and with the beginning of tick-tock > releases, this is a good time to get this in as a new feature. As for > configuring your existing system to not restart services on upgrade, see > https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt > for setting up a local policy to behave as you wish. > > -- > Michael >
