100x more webscale On Wed, May 18, 2016 at 11:02 AM, Horacio Duran <[email protected]> wrote: > For now we are trying to go around mongo issues that make the tests 100x > slower (yes one hundred) once this is fixed we should start using mongo 3.2 > exclusively since 2.4 iirc is EOL or near. The issue lies in the new storage > engine, which we could skip if mmapv1 ( the old one) wasn't also nearing EOL > I am currently on the phone but if You want more details I can dig up the > bug with details of what I am talking about. > > > On Tuesday, 17 May 2016, David Cheney <[email protected]> wrote: >> >> What's the plan for mongo 3.2 ? Will we be required to support 2.x >> versions for the foreseeable future, or is there a possibility to make >> it a build or run time failure if mongo < 3.2 is installed on the host >> ? >> >> On Wed, May 18, 2016 at 9:01 AM, Martin Packman >> <[email protected]> wrote: >> > On 17/05/2016, Curtis Hovey-Canonical <[email protected]> wrote: >> >> >> >> The juju-mongo2.6 package will be be preferred by juju 1.2.5 in xenial >> >> and without other changes, 2.4 will be used by all other 1.25 series. >> > >> > This isn't yet true, there's a bug open for it: >> > >> > "Use juju-mongodb2.6 for 1.25 on xenial" >> > <https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1570650> >> > >> > I had made the packaging change, but without juju code changes as well >> > it just went and installed the old (2.4) juju-mongodb anyway when >> > setting up a state server. >> > >> > Martin >> > >> > -- >> > Juju-dev mailing list >> > [email protected] >> > Modify settings or unsubscribe at: >> > https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
