Is Atlas having issues today?

MongoDB Atlas
, , ,
1

Is Atlas having known issues today? All afternoon my site has been going down for 5-10 minutes at a time to a point where things are significantly disrupted. When it’s down, I also cannot connect from my dev environment on localhost or from the Compass app. The errors I’m getting are:

error - MongooseServerSelectionError: connect ETIMEDOUT 54.227.xxx.xxx:27017
    at NativeConnection.Connection.openUri (/Users/adamjackson/Documents/birdinghotspots/node_modules/mongoose/lib/connection.js:825:32)
    at /Users/adamjackson/Documents/birdinghotspots/node_modules/mongoose/lib/index.js:414:10
    at /Users/adamjackson/Documents/birdinghotspots/node_modules/mongoose/lib/helpers/promiseOrCallback.js:41:5
    at new Promise (<anonymous>)
    at promiseOrCallback (/Users/adamjackson/Documents/birdinghotspots/node_modules/mongoose/lib/helpers/promiseOrCallback.js:40:10)
    at Mongoose._promiseOrCallback (/Users/adamjackson/Documents/birdinghotspots/node_modules/mongoose/lib/index.js:1288:10)
    at Mongoose.connect (/Users/adamjackson/Documents/birdinghotspots/node_modules/mongoose/lib/index.js:413:20)
    at connect (webpack-internal:///./lib/mongo.ts:87:78)
    at getStaticProps (webpack-internal:///./pages/index.tsx:498:65)
    at Object.renderToHTML (/Users/adamjackson/Documents/birdinghotspots/node_modules/next/dist/server/render.js:386:26)
    at async doRender (/Users/adamjackson/Documents/birdinghotspots/node_modules/next/dist/server/base-server.js:809:34)
    at async cacheEntry1.responseCache.get.incrementalCache.incrementalCache (/Users/adamjackson/Documents/birdinghotspots/node_modules/next/dist/server/base-server.js:926:28)
    at async /Users/adamjackson/Documents/birdinghotspots/node_modules/next/dist/server/response-cache/index.js:83:36 {
  reason: TopologyDescription {
    type: 'ReplicaSetNoPrimary',
    servers: Map(3) {
      'ac-s1ovtzi-shard-00-01.m629ebf.mongodb.net:27017' => [ServerDescription],
      'ac-s1ovtzi-shard-00-02.m629ebf.mongodb.net:27017' => [ServerDescription],
      'ac-s1ovtzi-shard-00-00.m629ebf.mongodb.net:27017' => [ServerDescription]
    },
    stale: false,
    compatible: true,
    heartbeatFrequencyMS: 10000,
    localThresholdMS: 15,
    setName: 'atlas-bexyua-shard-0',
    maxElectionId: null,
    maxSetVersion: null,
    commonWireVersion: 0,
    logicalSessionTimeoutMinutes: 30
  },
  code: undefined,
  page: '/'
}

And on Compass it says: connect ETIMEDOUT 34.201.190.214:27017

I’m on AWS with us-east-1. Strangely, when checking some the projects from my work that also use free atlas clusters, they’re not having issues, so I’m a bit confused why mine is having issues. Any suggestions on how to break out of those horrible cycle of going down every would be great. It’s down about half the time this afternoon.

2

Hi @Adam_Jackson,

I cannot see anything in the cloud status page that indicates an Atlas issue at this stage. However, it may be more cluster specific in which case I would recommend you contact the Atlas in-app chat support and provide them with the link to the cluster that is linked to your application that is generating the error logs provided.

Regards,
Jason

3

Thanks Jason,

I tried the in app chat support but never got a response, probably because I’m on the M0 free cluster (I take that back, I did now get a response suggesting it was related to elections, but I doubt elections last for 5-10 minutes?). I’ve tried switching to a new cluster in us-west-2 and so far so good. Hopefully that solves the issues. Would be nice to know what was causing the problems though.

4

Glad to hear you got a response. I’d recommend continuing to work with the Atlas in-app chat support team on the errors. If you haven’t already done so, please advise the details regarding switching to the new cluster in us-west-2 to the support team.

Best Regards,
Jason