Mongo 2.2.0 vs. 2.4.6 problem

[Gustavo Niemeyer]

And what is the actual issue?  2.2 must of course work with replica sets.
The mgo test suite is able to set it all up automatically, for example.
On Dec 19, 2013 5:40 PM, "Nate Finch" <nate.finch at canonical.com> wrote:

> BTW, I finally got ahold of some of the mongo people on #mongo, and it
> looks like it's just a bug in 2.2.0.  They say 2.2.0 is near EOL anyway.  I
> think we may have to just tell people that if they want mongo in a replica
> set, they need to be on a version higher than 2.2.0 (notably, I tried 2.2.6
> and it works just fine).
>
>
> On Thu, Dec 19, 2013 at 1:53 PM, Nate Finch <nate.finch at canonical.com>wrote:
>
>> I'm getting a weird failure running some tests to set up mongo in a
>> replica set from a locally running instance of  Mongo.  The tests pass in
>> 2.4.6, but fail in 2.2.0.  Mongo output for each is here:
>> http://pastebin.ubuntu.com/6596052/    The 2.2 instance fails with "all
>> members and seeds must be reachable to initiate set".  Anyone have any
>> suggestions for making this work in both 2.2 and 2.4?
>>
>> This is a minimal implementation that shows the difference: (works
>> against mongo 2.4.6, fails against 2.2.0).
>>
>> http://pastebin.ubuntu.com/6601155/
>>
>> Anyone on this list know Mongo well?  I've lost a lot of time trying to
>> figure this out.
>>
>> -Nate
>>
>
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20131219/6d4403dd/attachment.html>