Hi, An exponential back-off algorithm is a good option. I would recommend that instead of just waiting 30 seconds, move to another user and come back later. For example using a priority queue based on earliest start time. Also you can increase the number of thread to around 10-15.
Another option, is to try IMAP mail migration and compare timings: http://www.google.com/support/a/bin/answer.py?hl=en&answer=61369 Julian. On Jun 26, 9:47 pm, Patrick <[EMAIL PROTECTED]> wrote: > As a follow-up to my earlier post, I've done a lot of work today to > get my code to properly do exponential back-off, as well as wait 30 > seconds between migrating message feeds. > > I even break up individual batch feeds into no more than 15 messages > (250KB) or so, and get these 503 errors for almost every other message > in the feed (when I parse the results that I get back). > > It's very confusing that only *some* messages in the feed generate > those 503 errors. It's ridiculous that I can't migrate a few MB of > mail without it failing. > > At this point, this will likely hold up our entire organization's move > to Google since we can't help our students move their mail. > > On Jun 26, 6:50 am, Patrick <[EMAIL PROTECTED]> wrote: > > > My organization (an .edu) is planning to let our population opt-in to > > Google during the beginning of our transition. We have a large > > population we’re planning to move within 2 weeks (probably 5000-10000) > > users each with no more than 50MB mailboxes each (more realistically, > > an average of 20 MB or so each). > > > Part of the transition is for users to choose if they want mail > > migration or not. If they do, we have a back-end process that runs > > and migrates their mailbox (using the Mail Migration API). > > > The migration is performed using the Google domain admin account, and > > we’re planning on a few concurrent processes to be running from one > > server (1 IP address). > > > When a “503” (server busy) error is received for a message in one of > > the feeds, we’re planning to program in an exponential back-off > > routine (e.g., wait 30 seconds, then 60 seconds…). > > > However, the Google Mail Migration API documentation isn’t very clear > > on the volume of mail that would generate such an error, nor what > > factors could cause it. > > > If we have 5 concurrent migrations happening from 1 IP address, is > > that going to increase the odds of getting that “503” error? If so, > > this could drastically affect our strategy for moving our population > > to Google. And if so, is there the possibility that we could contact > > Google and ask for some restrictions to be either lifted or altered > > for our IP addresses for a period of time? > > > Thanks! > > Patrick > > > On Jun 25, 10:23 am, "Julian (Google)" <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > You may be getting the error because you are posting emails too fast, > > > please try to slow down the migration and let me know if the problem > > > persists. > > > > Thanks, > > > Julian > > > > On Jun 24, 10:51 am, Bam <[EMAIL PROTECTED]> wrote: > > > > > Hi All, > > > > > I have a problem when to use Email Migration API with .NET Client > > > > Library. > > > > > Not all message can be posted correctly to gmail. > > > > > i get response. > > > > > "The server is currently busy and could not complete your request. > > > > Please try again in 30 seconds.#503" > > > > > How to ignore or resolved this problem?? > > > > > Thanks,- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text - > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
