My stats updated today, 10 hours ago, hope you all get it fixed!
On Wednesday, September 25, 2013 9:47:38 AM UTC+2, timh wrote:
Yeah stats still not updates..
I wonder if it has anything to do with the upgrade to 1.8.5 runtime, plus
all the scheduler instability.
T
On Monday, September
Yeah mine where updated earlier today.
T
On Monday, September 23, 2013 7:55:19 PM UTC+8, timh wrote:
Howdy
Normally stats are only a couple of days old, but I am up to 4+ days and
no updated datastore stats.
Anyone else seeing this ?
T
--
You received this message because you are
Yeah stats still not updates..
I wonder if it has anything to do with the upgrade to 1.8.5 runtime, plus
all the scheduler instability.
T
On Monday, September 23, 2013 7:55:19 PM UTC+8, timh wrote:
Howdy
Normally stats are only a couple of days old, but I am up to 4+ days and
no updated
I have the same issue here, you are not alone.
On Monday, September 23, 2013 1:55:19 PM UTC+2, timh wrote:
Howdy
Normally stats are only a couple of days old, but I am up to 4+ days and
no updated datastore stats.
Anyone else seeing this ?
T
--
You received this message because you
Yup - 5 days ago for us. Our Billing (Usage History) is also 5 days
behind. Probably related to the 1.8.5 rollout.
j
On Monday, 23 September 2013 05:55:19 UTC-6, timh wrote:
Howdy
Normally stats are only a couple of days old, but I am up to 4+ days and
no updated datastore stats.
Anyone
Have you got sessions enabled?
I believe (and it's a long time since I've used them) that if you have
sessions enabled, they won't show up in the datastore viewer. However, they
do get written out to the datastore for replication out to your instances.
--
You received this message because
This can happen if you used to have a lot of entities and deleted them
and the statistics haven't updated yet to reflect the new number. Try
waiting a day to see what the new number is.
If you are referring to the estimated data store writes for your
application under the new pricing scheme, you
I've seen a similar thing and have been waiting many, many days
(weeks?).
I'm wondering if datastore stats are somehow measured over the raw
BigTable entities which don't actually get scraped up for a long
period of time.
If so, one would only really notice this discrepancy if they've done a
This problem has been outstanding for many days, perhaps weeks ...
lol ... trying to see if the problem still exists today and getting
status 500 on gae dashboard ...
meanwhile ... gae upgrades are not working either ... and python just
got a big ? in gae status ...
rough day in gae-land
On
I think the first graphs speak a lot to what many users are
experiencing. It may be before 'fails' were rather mild, and just
meant an extra 400 ms, but now, 'fails' are very hard and deadly.
I don't agree that only customer facing applications are affected, any
application that requires
Do we need to enable the datastore stats?
I tried the sample code (java) in both dev and production, and the
globalStat is always null.
DatastoreService datastore =
DatastoreServiceFactory.getDatastoreService();
Entity globalStat = datastore.prepare(new Query
(__Stat_Total__)).asSingleEntity();
11 matches
Mail list logo
