On 15:09 Mon 18 Jan     , László Böszörményi wrote:
> Hi,
> 
> On Mon, Jan 18, 2016 at 1:29 PM, Apollon Oikonomopoulos
> <apoi...@debian.org> wrote:
> > As far as the MongoDB 2.4 to 2.6 transition goes, it is supported
> > upstream[1] as a "binary-compatible “drop-in” upgrade" and
> > application-side compatibility can be checked in advance by running
> > db.upgradeCheckAllDBs() on a 2.6 client connected to the 2.4 server. In
> > that respect, the transition is far less of a problem than the
> > 2.0-to-2.4 transition needed for a Wheezy to Jessie upgrade. That said,
> > I'm in favor of uploading 2.6 to unstable using the mongodb source name
> > (and not mongodb-2.6) and then providing a Jessie backport.
>  The Wheezy -> Jessie path missed the 2.2 version and providing
> mongodb-version package names helps to avoid this.
> But sure, let the names remain as-is.

Unfortunately, there seems to be no easy solution for this problem.  
Since upstream only supports transitions between consecutive stable 
releases, Debian should really provide packages for all intermediate 
versions to facilitate upgrades. But yes, in the Wheezy -> Jessie case, 
using a different package name (although not source name), would at 
least guarantee that no automatic upgrades would take place.

> 
> > Since we are in the process of upgrading to MongoDB 2.6 at work, I've
> > rolled out a 2.6.11 package, trying to benefit from the changes done
> > both in Ubuntu and László's updated package.
>  May you share your experience? Any manual interaction was needed?

Sofar I've run db.upgradeCheckAllDBs() against one of our clusters with 
a 500 GB dataset and tens of millions of documents. All-in-all it 
emitted errors regarding mostly dots in field names (which has been a 
restriction since at least 2.2) and just 4 (!) key-too-long documents.  
I've seen RDBMS migrations that are much worse than this, plus at least 
now we can get a glimpse of what we should fix *before* actually 
upgrading the server :).

> > I've already tested the clients on our infrastructure, and we
> > will start rolling out the server package soon on Jessie.
>  Please keep us posted.

We will soon upgrade our development instances, so I will let you know.

Regards,
Apollon

Reply via email to