Backup running wild

[Rüdiger Jungbeck]

We have an AppEngine based Python application which has 212 MB of data store data (according to the console).

I tried to do a backup every 10 days.

- description: My Backup
  url: /_ah/datastore_admin/backup.create?name=BackupToCloud&kind=Application&kind=Design&kind=JobQueue&kind=Journal&kind=License&kind=Token&kind=User&kind=Wiki&filesystem=gs&gs_bucket_name=lpsngbackup
  schedule: every 240 hours
  target: ah-builtin-python-bundle

The backup worked successful for several month.

Suddenly thousands of daily /_ah/mapreduce/controller_callback/.... requests are in the console (our app doesn't do mapreduce).

The console says that we had >420.000 of these requests yesterday alone.

Where do they come from, how do I stop them?

My bills doubled in the last month.

[Adam]

Those MapReduce calls are actually part of the Datastore Backup:

Very frequent backups often lead to higher costs. When you run a Datastore Admin job, you are actually running an underlying MapReduce job. MapReduce jobs cause frontend instance hours to increase on top of Storage operations and Storage usage. To keep an eye on your resource usage: 

1. Visit the Cloud Platform Console Dashboard page
2. Use the pulldown menus at the top of the page to select the default module and the ah-builtin-python-bundle version

[Adam]

I forgot to add, you can stop the running backup from the Developers Console in the Datastore Admin screen:

Aborting a backup
If Backup jobs are currently running, they appear in a Pending Backups list in the Datastore Admin screen. You can stop these running backups by selecting the backup in the list and clicking Abort. 

Cheers,

Adam

Cloud Platform Support

On Friday, December 4, 2015 at 2:52:53 AM UTC-5, Rüdiger Jungbeck wrote: