Your message dated Sun, 23 Feb 2020 22:22:57 +0000
with message-id <[email protected]>
and subject line Bug#947743: Removed package(s) from unstable
has caused the Debian Bug report #725825,
regarding mongodb-server: No safe upgrade path from Wheezy to Jessie when using
sharded cluster
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
725825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725825
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mongodb-server
Version: 1:2.4.5-1
Severity: normal
Hi,
Just FYI (but maybe you are already aware of that), there is no safe
upgrade path from 2.0 to 2.4 on a sharded cluster. When the Mongos are
upgraded, they will fail to upgrade config servers metadata, as they
assume the metadata is 2.2 format. According to upstream, the upgrade
path from 2.0 to 2.4 when using a sharded cluster is to upgrade to 2.2
first : http://docs.mongodb.org/manual/release-notes/2.4-upgrade/
The problem is, not only is it not supported, but the metadata will get
corrupt.
I'm not sure what the best way to deal with it would be. At the very
least, the users should be warned. If a sharded cluster is detected,
upgrade should be interrupted to prevent data loss. Unattended upgrade
in a cluster is out of the question, but maybe we can provide a safe way
to do it (I'm not yet sure of what mongos --upgrade does), via script or
otherwise.
Cheers,
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mongodb-server depends on:
ii adduser 3.113+nmu3
ii libboost-filesystem1.49.0 1.49.0-4+b1
ii libboost-program-options1.49.0 1.49.0-4+b1
ii libboost-system1.49.0 1.49.0-4+b1
ii libboost-thread1.49.0 1.49.0-4+b1
ii libc6 2.17-92+b1
ii libgcc1 1:4.8.1-10
ii libgoogle-perftools4 2.1-1
ii libpcre3 1:8.31-2
ii libpcrecpp0 1:8.31-2
ii libsnappy1 1.1.0-1
ii libstdc++6 4.8.1-10
ii mongodb-clients 1:2.4.5-1
mongodb-server recommends no packages.
mongodb-server suggests no packages.
-- no debconf information
--
Clément Hermann (nodens)
--- End Message ---
--- Begin Message ---
Version: 1:3.4.18-2+rm
Dear submitter,
as the package mongodb has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/947743
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
