New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cant connect mlab replicaset #48
Comments
Sorry about this @sezgin, we didn't implement replica support yet. I can start working on the feature tomorrow afternoon at best. But I'll need to set up a replica first, which is going to cost me some time as well. Best case scenario we'll have the feature implemented somewhere next week... but in MongoKitten's beta branch. We've been (re)working/optimising a lot lately, and backporting this would be a major pain. |
Which MLab subscription are you using? This might be useful information for me if I decide on hiring a testing bench. |
https://www.mlab.com/plans/ Thanks all. |
I definitely can't afford one of those 😬 But I'll have a look if I can manage to afford a shared replica for 15 dollars a month. I'm unsure if success on my side would translate into a success on your scale as well... but that's a worry for later. |
its same not free plans. you can test it, i think it give same result other plans, and mongokitten good now but it will be amazing 👍 |
Are you using SSL on your server? If that's the case then you should be using our beta 2.0.0. It'll be changing a lot in the coming days still. So if you're using this I'd recommend not running a production environment. But it'll have support for SSL when using |
Was this implemented? I am also trying to connect to a replica set on mlab. Using one of the $15 a month plans in mLab. |
@gabriellanata it's not implemented as I don't have the financial capabilities to fund any (replica) servers at the moment. |
I can create a mlab database with a replica set so you can use it for a few weeks to develop this functionality, if that is something you'd be willing to do. I know this is a feature that many users will not need, but i'd be very grateful as it is something we need to be able to scale in the future. |
That would be really helpful for me! I could definitely use that to develop Replica Set functionality. |
Sure! How can I contact you to share the details privately? |
Using my email address at joannis@orlandos.nl |
Working on it now! Thanks @gabriellanata |
@gabriellanata I've got connection string parsing working now and am able to connect to the first host in the replica set. I'll continue now to implement selecting the secondary. And I'm thinking of adding support for efficient querying so that read-only queries will not be sent exclusively to the primary but also to the secondaries, since they should have the same data. |
Which MongoKitten version do you run @gabriellanata ? |
Awesome! mLab is running the latest version it allows: 3.2.11 |
Are you using MongoKitten directly? Is there a need to back port these features to an earlier MongoKitten version? I'm working on the soon-to-be-released MongoKitten 3 branch for this feature now. |
Oh sorry I thought you meant mongoDB version. I am currently running MongoKitten 2, would you consider MongoKitten 3 stable enough right now? We're still in a beta stage until the end of the year so I don't need this feature right this second. I have no problem with upgrading to version 3 as soon as it is available. |
I wouldn't consider MongoKitten 3 to be stable yet in every way. Aggregates are being worked on hard currently. The rest should be good to go. I'll work this into MongoKitten 3 now 👍 I've been able to query the collections now and am working on the more advanced parts of replica set support. Amazing entries into the collection! 😂 Everyone around me look up when I laughed at that 😛
|
@gabriellanata it's working! |
@gabriellanata If you'd like you can test MongoKitten alpha4 using I'll need to experiment a bit more before I'd mark it as "working", specifically with MongoKitten 3 coming soon with many changes still happening. More advanced features have not been tested yet using replicas for example. But I'll work towards it and I'll poke you when it works so that my testing instance can be disabled again. |
I'm having trouble with emulating a disconnected primary server scenario. MongoDB should search for the primary again in the available provided servers. |
I just sent you an email with info on how to access the mlab account and simulate a fail over |
this example is my problem
server = try Server("mongodb://heroku_xxxxx:xxxxxxx@serveraddress.mlab.com:23372,serveraddress-a1.mlab.com:23372/xxxxxxx?replicaSet=rs-xxxxxx", automatically: true)
thow error, MongoDB is not available on the given host and port Socket failed with code 61 ("No data available") [connectFailed] "Unknown error"
The text was updated successfully, but these errors were encountered: