[CASSANDRA-10872] Debian Package does not prompt the user to review the config files; it just replaces them causing trouble (since the daemon starts by default)

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Not A Problem
• Component/s: Packaging
• Labels: debian packaging

Environment

Ubuntu 12.04, Cassandra 2.0.16 -> 2.0.17

• Severity: Critical
• Assignee: Michael Shuler
• Reporter: Vasilis

Authors

Michael Shuler

• Created: 15/Dec/15 09:24
• Updated: 16/Apr/19 09:30
• Resolved: 20/Oct/16 18:23

Description

We run Cassandra 2.0.16 on Ubuntu 12.04 and were trying to upgrade to 2.0.17 due to CASSANDRA-9662. The problem is that during the upgrade the we were not prompted how to handle cassandra-env.sh and cassandra-rackdc.properties.

The output from the upgrade:

...
Setting up cassandra (2.0.17) ...
Installing new version of config file /etc/cassandra/cassandra-env.sh ...
Installing new version of config file /etc/cassandra/cassandra-rackdc.properties ...
vm.max_map_count = 1048575
net.ipv4.tcp_keepalive_time = 300
...

This meant that the nodes started automatically after the install with the wrong DC name.

I don't think that these config files should have been replaced without the admin being asked; this doesn't appear to comply with standard Debian packages.

Secondly if CASSANDRA-2356 was implemented the problem would not be as severe; i.e. it would be possible to workaround this issue. Whereas currently, there is no way to prevent the node when upgraded from starting in the wrong DC.

Issue Links

• is related to: CASSANDRA-2356 make the debian package never start by default