Migration DB Stuck

[talkaboutdesign]

Was trying to migrate data to MongoLabs and pressed cancel during the process. Typed in wrong url.

Now I am stuck on this screen and can't retry the process.

[gfosco]

cc @drew-gross

[jamesyu]

yep this is a bug, we're working on it

[francocorreasosa]

+1

[jamiechapman]

+1, the UI allowed me to retry today — after about 20 minutes of migrationState=1 (with a 4 month secondsRemainingStr) the export eventually failed to state 7 and showed up as cancelled in the web UI.

We're using a mongolab M1 instance with failIndexKeyToLong set as suggested in the guide with SSL too. We have roughly have about 40 million objects stored on Parse, so I'm wondering if the process which 'snapshots' the data is somehow timing out and thus causing the migration to prematurely cancel itself?


[JcMinarro]

+1

[talkaboutdesign]

FYI, mine is stuck on this screen for a day.

[JcMinarro]

It is broken. I have done a new proyect with only 2 installations and 2 users and it does not work.
I am on the smae screen @talkaboutdesign

[gfosco]

Ok, sorry about this delay... Checking on the status of this tool internally.

[aaronrau]

Hi, I was trying to migrate data to MongoLabs as well but to their Shared Plan unfortunately it failed and is stuck.

Turns out that from their support team, the Shared Plan failedIndexKeyToLong is set to true.

Is it possible to get an error log from the migration tool to show that my migration is failing due to this setting? MongoLabs is willing to change that parameter.

[talkaboutdesign]

Still same after 36 hours.

[hafizapp]

How can I re-initiate the migration process?

Now I am stuck on this page. Please help

@jamesyu

[francocorreasosa]

@hafizapp Go to App Settings and start the migration again. It works fine.

[hafizapp]

@francocorreasosa I am really sorry, still it showing this for me. And it don't allow me to start the migration process again.

Thanks

[gloos]

same here, it just gets stuck

[hafizapp]

@francocorreasosa Thank You.

Just noticed. Instead of going migration. You have to go -

App Settings -> Migrate

[RafaRuiz]

I'm experiencing something different:

My database got migrated 100% with green ticks to say it was OK.

But now my app doesn't work. These are some logs, which are not taken anymore:

This morning I tried to load the old dashboard, but can't load the database. Now I see an error 500:

and if I see the collections:

This is when I load the new dashboard:

[tredman]

@RafaRuiz - in your case there appears to be an authentication error. We are unable to connect to mongo using the credentials that you provided. Can you check the username/password you provided and your mongodb connection string? You can force-change your mongodb connection string under "App Settings" in the Parse dashboard.

[jamiechapman]

@tredman could you possible check why our db export is failing too? https://dashboard.parse.com/apps/minecraft-explorer-pro ([email protected]), I asked the nice folk over at mongolab to make sure all my settings are correct and everything seems fine. Is it a Parse bug or am I doing something wrong? Thanks!

[skinp]

@jamiechapman your particular issue seems to be a known bug with the migration (source replicaset not found). We're working on a fix for this.

[jamiechapman]

@skinp — thanks so much for the clarification, we've been a bit worried that it was something our end that was at fault. We'll wait for a fix in that case. Cheers.

[tredman]

@jamiechapman - the fix is live, please try again at your convenience.

[jamiechapman]

Perfect, thanks @tredman — started the migration again and I can see collections being made into the database as we speak.

[jamiechapman]

@tredman — it started to go horribly wrong, each object had this error:-

"Skin": {
        "Name": "Skin",
        "State": 7,
        "StateReason": "EnsureEmpty issue: not authorized on skinstudio to execute command { count: \"Skin\", query: {} }",
        "BatchSize": 1000,
        "ExpectedDocumentsApprox": 1221975
      },

I've cancelled the migration and setup a new connection string using the root user instead, but the UI now says Migration already in progress. (even though it isn't?).

[tredman]

@jamiechapman - the job automatically retried a number of times before it was finally stopped. At the moment, it doesn't appear to be in an in-progress state. Can you please try again? Note that if a previous migration failed, you will need to drop any documents on the destination before beginning a new migration, or it will return an error.

[jamiechapman]

Hmm, thats a bit weird @tredman.

1. I've dropped all collections in the database using mongolab.
2. The "Migrate" button is clickable in App Settings.
   
3. I entered the connection string again (+ verified it works via another tool), but it says Migration already in progress.
   
4. I checked the /migrations REST endpoint to see what the deal was and its in state 9, does that mean anything? It's weird how the migration still appears to be running but the Web UI is trying to let me start again.
   

[gloos]

I confirm I was stuck and I've just tried migrating again but I get a Migration already in progress error.

edit: there are no collections on my server.

[tredman]

We've identified a UI bug with certain job states. A fix is coming shortly.

[RafaRuiz]

@tredman I can't modify the connection string under App Settings, there's no field to change it. I just can click on Migration and it shows the success of migration. What else can I do?

My apps are still down since almost 2 days ago, please guys I'd need a solution.

@RafaRuiz - in your case there appears to be an authentication error. We are unable to connect to mongo using the credentials that you provided. Can you check the username/password you provided and your mongodb connection string? You can force-change your mongodb connection string under "App Settings" in the Parse dashboard.

[gfosco]

We discussed this here and basically in order to deal with migration issues, we need you to individually report a bug through parse.com/help. This allows each of you to get individual support, from a team who can escalate issues, and for us to be able to ask up front for specific information which will help us handle your issue. We're exposing the 'job id' for the migration in the UI, and that is something you should provide if you're having a problem.

Going to close this issue. For problems involving migration, or any issues not specific to parse-server, please visit https://parse.com/help and find the bug icon / "Something wrong?" section to start the bug reporting flow.

[taijizhu]

any updates on this?

[francocorreasosa]

@taijizhu This was resolved on Feb 3.

[IbrahimDisouki]

Also i have the same issue but the migration stuck on "Sync" and i can't finalize the migration.

[hramos]

A migration job stuck in sync usually points to insufficient hardware or high latency between api.parse.com and your target database.

Please report any migration issues at https://parse.com/help. We'd like to keep the discussion here centered around Parse Server itself.

[zyg-github]

I have the same issue(in the sync state above 12 hours), and is there any log that we can know what's the real problem is?

[hramos]

@zyg-github see my answer above.

[zyg-github]

@hramos If the problem points to insufficient hardware or high latency between api.parse.com. But why can i get the sync speed so high. 416rows/s befor and 1.71krows/s now?

[hramos]

@zyg-github you inquired about a log with additional information. Contacting us via https://parse.com/help#report with your job id is the best way to get more details on what is wrong with a specific migration.

[zyg-github]

@hramos

[Treybro]

I'm currently in the process of migrating a live production mobile application from Parse to Azure using the Migration Tool provided by the good folk at Parse, however I'm getting stuck on the "Sync Phase".

I'm getting all green lines indicating a successful transfer of the data, however when the migration tool is checking for any new writes, it fails with the following error:

"There was a problem with the migration."

Parse documentation doesn't have any information on the above, so I would appreciate your help!

I'm running my Azure server and Document DB instances on the S3 (Standard: Large) with Auto scaling, and the Document DB implementation is on Pricing Tier S3 (THROUGHPUT (RU/s) 2500)

[hramos]

@Treybro see my last three posts in this issue - you'll want to use the Parse bug reporting tool.

[zyg-github]

@Treybro
I also encountered the same problem. You solve the problem yet?