2 years ago
I ran into this issue while trying to push an update. The server keeps crashing regardless of what I try. I rolled back to an older update (6 weeks old) and things work fine. I have a "DEV" env that is on railway as well, however that env uses mongoAtlas directly instead of using the service on railway and no issues there. Any help would be greatly appreciated. Thank you.
ProjectID: dd3f3852-bec4-439c-b5a8-0765d555c6dc
12 Replies
2 years ago
the default MongoDB database is not a replica set, if you need a replica set please use this template that a team member has put together -
2 years ago
databases cannot have replicas
2 years ago
you need to use the template I link if you need a mongo replica set
I dont and to my knowledge the only place I see it is in the railway settings.. is that where this is coming from ?
2 years ago
read my first message again please
2 years ago
my answer remains the same, again, if you need a mongo replica set you need to deploy the template
2 years ago
it has nothing to do with the replica setting in the service
I dont need replica set, I've double checked my codebase and it's not configured, setup, initialized or other there, I asked about the service related replica setting as that is the only thing even remotely close to the issue.
2 years ago
please read your own error logs, it clearly states that what you're doing requires a mongo replica set.
again none of this has anything to do with the replica setting in the service, that's something else entirely.
just incase anyone else runs into this issue, it was being caused by .watch() which uses mongoDB change streams.