Mongodb randomly crushing
lumieowo
PROOP

a year ago

/app/node_modules/mongodb/src/sdam/topology.ts:610

const timeoutError = new MongoServerSelectionError(

^

MongoServerSelectionError: connection <monitor> to ip:27017 closed

at Topology.selectServer (/app/node_modules/mongodb/src/sdam/topology.ts:610:30)

at async executeOperation (/app/node_modules/mongodb/src/operations/execute_operation.ts:142:18)

at async ChangeStreamCursor.getMore (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:672:12)

at async ChangeStreamCursor.getMore (/app/node_modules/mongodb/src/cursor/change_stream_cursor.ts:159:22)

at async ChangeStreamCursor.fetchBatch (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:730:24)

at async ChangeStreamCursor.next (/app/node_modules/mongodb/src/cursor/abstract_cursor.ts:398:7) {

reason: TopologyDescription {

type: 'ReplicaSetWithPrimary',

servers: Map(3) {

'ip:27017' => [ServerDescription],

'ip:27017' => [ServerDescription],

'ip27017' => [ServerDescription]

},

stale: false,

compatible: true,

heartbeatFrequencyMS: 10000,

localThresholdMS: 15,

setName: 'atlas-jvmrvt-shard-0',

maxElectionId: ObjectId { buffer: [Buffer [Uint8Array]] },

maxSetVersion: 80,

commonWireVersion: 0,

logicalSessionTimeoutMinutes: 30

},

code: undefined,

[Symbol(errorLabels)]: Set(0) {},

[cause]: MongoNetworkError: connection <monitor> to ip:27017 closed

at Connection.onClose (/app/node_modules/mongodb/src/cmap/connection.ts:295:18)

at TLSSocket.emit (node:events:517:28)

at TLSSocket.emit (node:domain:489:12)

at node:net:350:12

at TCP.done (node:_tls_wrap:657:7) {

[Symbol(errorLabels)]: Set(1) { 'ResetPool' },

[cause]: undefined

}

}

Solved

7 Replies

brody
EMPLOYEE

a year ago

Hello, I don't see a mongo database deployed anywhere in your personal account or your team.

Can you help me understand what Mongo database you are referring to here?


Status changed to Awaiting User Response Railway about 1 year ago


lumieowo
PROOP

a year ago

My team has a project using an atlas managed db


Status changed to Awaiting Railway Response Railway about 1 year ago


brody
EMPLOYEE

a year ago

Ah okay, that wasn't clear.

Have you whitelisted your static IP in Atlas?


Status changed to Awaiting User Response Railway about 1 year ago


lumieowo
PROOP

a year ago

No, my atlas has it on every ip is whitelisted setting,

The project is running fine until it randomly crashes


Status changed to Awaiting Railway Response Railway about 1 year ago


brody
EMPLOYEE

a year ago

Is it currently running connected to Atlas?


Status changed to Awaiting User Response Railway about 1 year ago


lumieowo
PROOP

a year ago

Yes, last time it crashed Im pretty sure was yesterday when we had 45con current users, I restarted and it continued to run smoothly ever since


Status changed to Awaiting Railway Response Railway about 1 year ago


brody
EMPLOYEE

a year ago

From the information given, it seems like your application struggled to keep an outbound connection open under load, perhaps you can look into adding replicas to horizontally scale your application.

But I can assure you this error was not a fault of the platform, we do not under any circumstances close outbound connections, nor do we have the ability to do that.


Status changed to Awaiting User Response Railway about 1 year ago


Railway
BOT

6 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 6 months ago


Loading...