I have two projects where I made a GitHub Deployment setup. Both were working fine but then I upgrade one from shared to a dedicated cluster. After that upgraded project deployments stopped working with the error Failed to Deploy: cannot change the linked Atlas cluster while sync is not terminated. I tried to pause/terminate/launch sync and deploy from UI but without any success.
Not sure if it’s related but during the upgrade, sync stopped working with errors:
translator failed to complete processing batch: failed to update resume token document: (AtlasError) cannot find user account after reload
recoverable event subscription error encountered: error making mongo client to register translator handler: error connecting to MongoDB service cluster: error parsing uri: lookup _mongodb._tcp.xxxxxxxx.xxxxx.mongodb.net on xx.xxx.x.x:xx: no such host
encountered non-recoverable resume token error. Sync cannot be resumed from this state and must be terminated and re-enabled to continue functioning: (ChangeStreamHistoryLost) Resume of change stream was not possible, as the resume point may no longer be in the oplog.
After that, I disabled deployments and had to terminate sync which was a bad experience for our users. At this point, I’m also afraid to anyhow update MongoDB’s plan.
I got a reply from the chat support:
It looks like this issue is already raised internally as realm-cli fails to find diff when updating "enabled" field of hosting/config.json
It may take some time to resolve it.
Right now I must deploy to production manually using UI which is error-prone and stressful. And since I don’t know when the issue will be fixed or if it was already fixed I also need to manually try it from time to time which, again, stressful and cumbersome.
I hope to at least receive a reply when the fix for deployments will be done. Thanks.
My name is Josman and I will try to help you with your issue. Could you please tell me the following:
Both were working fine but then I upgrade one from shared to a dedicated cluster
Have you terminated Sync before upgrading? At this moment, when you upgrade from a Shared to a Dedicated Cluster you need to terminate, upgrade your cluster, and then re-enable Sync. If you don’t perform these operations, you will receive the error you mention in the description of your issue:
translator failed to complete processing batch: failed to update resume token document: (AtlasError) cannot find user account after reload
Could you please let me know if you have hosting enabled? and if so, what is your current situation?
Hi @Josman_Perez_Exposit , you are right I didn’t follow the upgrade guide you mentioned. I probably miss some kind of warning about it somewhere.
You are right I have hosting enabled. My situation is that automatic deployment doesn’t work and I change everything manually using UI.
Hi @Josman_Perez_Exposit . So, am I doomed? There seems to be no known workaround. Should I create a different project? Will it be possible to transfer my paid plan?
Hello @Anton_P , in order to help you in the best way possible, if you have a developer or greater plan, could you please open a support ticket to assist you with this issue? I want to be able to access your Realm Application to study why you cannot enable automatic deployment on this particular Realm App.
Please let me know if you have any additional questions or concerns regarding the details above.
Thanks for your reply @Josman_Perez_Exposit . Sadly, I have a basic support plan, and paying for a higher support plan just to ask to fix bugs in your system doesn’t seem fair enough. If you need something like app ID or project ID or anything else I can message you directly. If that won’t work then let it be so.
No worries, if you can share both app id and project id, that would help me investigate what could be causing the unexpected behaviour in your Realm application.