cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasilis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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)
Date Wed, 16 Dec 2015 17:20:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060339#comment-15060339
] 

Vasilis commented on CASSANDRA-10872:
-------------------------------------

Have you been able to reproduce it [~mshuler]? This morning I installed Ubuntu 12.04 on two
VMs, copied the 2.0.16 debian package from the live cluster, installed it using _dpkg --install
<package.deb>_, did an update/upgrade in order to go to 2.0.17 and I got different behaviour...
I wasn't prompted but the files were not replaced this time. I cannot understand why yet,
but I hope this might be useful to you? Have I done something stupid here???? I followed exactly
the same path in order to go from _2.0.16 -> 2.0.17_ in both scenarios. I also checked
that the 2.0.17 package that I got from my _cassandra.list_ found in _/var/cache/apt/archives_
is the same as the one in the live cluster.

On a side note, I was under the impression that DC name cannot change once set according to
the [documentation|http://docs.datastax.com/en/cassandra/2.0/cassandra/initialize/initializeMultipleDS.html],
but then I found CASSANDRA-9474, which in a way I am happy it hasn't been fixed for 2.0.x.
So, I just changed the _cassandra-rackdc.properties_ and it looks like it worked for me.

> Debian Package does not prompt the user to review the config files; it just replaces
them causing trouble (since the daemon starts by default)
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10872
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10872
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Ubuntu 12.04, Cassandra 2.0.16 -> 2.0.17
>            Reporter: Vasilis
>            Assignee: Michael Shuler
>            Priority: Critical
>             Fix For: 2.1.x
>
>
> 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 ...
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message