Crons live on after app migration.

[John Gardner]

I've noticed one of my apps with too many cron jobs running; I changed a schedule from every 30 minutes to 1 time a day recently. The jobs are still running all day long.

This app used the app engine migration process to migrate from Master/Slave to HR.  It seems that the cron jobs on the M/S appid are now running against the new app, even though the old app is disabled(!).  Disabling an app should also disable cron jobs, IMHO.

I've apparently been paying for instance time for double the cron load for weeks now.  Hopefully someone else can learn from this.

My workaround is to re-enable the old app, empty out the crons, update crons, and disable the app again.  I'd like to see this as part of the migration process.

John

[Jason Collins]

I fought with this for a long time too:

http://groups.google.com/group/google-appengine/browse_thread/thread/19d863a7c74ef12f/69a55b3afd484fde

For me, it looked like HRD was using double writes - which it was not.

It's a difficult to diagnose issue which will probably impact most who
use the migration tool. "difficult to diagnose" because I think it's a
fair assumption that disabling an app will also disable its crons.

j