Probably you are right. But the problems must be in both map reduce jobs. I'm going to explain why I think that.
1. Last friday (June 8th) we tried to optimize our database which was 1,19 Gb.
2. We couldn't see the results of that job because the stats weren't updated, and in the Dashboard still said 1,19 Gb.
3. Yesterday (June 12th) the stats weren't update and Dashboard still said 1,19.
4. Today (June 13th) seems that map reduce job of friday finished because stats says that last updated was 5 days ago (yesterday was 6 days ago). However the Dashboard still says 1,19 Gb.
Why happen all these? Isn't an efficient way to manage the Datastore?
How can be so slow?
El lunes, 11 de junio de 2012 22:47:50 UTC+2, Chris Ramsdale escribió:
Datastore statistics and billing data are generated by separate map reduce jobs. Currently there is an issue with the job that updates the datastore stats on a daily basis, and we're investigating potential fixes. I'll send out an update as soon as we have more information.
Last updated: 6 days, 5:32:22 ago and increasing!!!
Can anyone explain me how can be the billing updated if the statistics hasn't been updated for 6 months??
El lunes, 11 de junio de 2012 12:36:36 UTC+2, Marcel Manz escribió:
Hi Takashi
I would be really happy if the issue with the missing per-kind statistics could finally get fixed:
http://code.google.com/p/googleappengine/issues/detail?id=6571
Since months my application only lists statistics for 'All entities' and its pretty annoying to optimise datastore usage without seeing any per-kind statistics.
Thanks for looking into this.
Marcel
We're aware of this issue. Now the datastore stats are updated less often than it should be.
We'll followup with more detailed information shortly.
Sorry for the inconvenience.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/N0J6XqssZjkJ.