Honestly this doesn't seem worth spending a lot of time debugging. Google doesn't guarantee any finite limit to "eventual" consistency; even if it works within the 10s window 95% of the time, it will certainly fail eventually.
Seems like Cloud SQL is the next thing to try, and barring that, put the collector in another cloud host using something that can handle the throughput. Jeff On Thu, Aug 2, 2012 at 9:29 AM, hyperflame <[email protected]> wrote: > It's just odd that GAE is having trouble not when load is high, but > when load is low. I doubt tablet issues are the cause here. Can you > run some fake load against the datastore? Just build a B1 that adds > some fake scores, and have your tabulator backend delete those fake > scores when it builds the leaderboard. > > Also, i'm wondering why it just started 5 days ago. Did your load > profile change? Try this: change your instances to F2, then back to > F1. Perhaps your resident instance got moved to a faulty server 5 days > ago; this will force GAE to open a new instance on a new server. > > On Aug 2, 9:50 am, Richard <[email protected]> wrote: >> Kinda. By 'low load', I mean 150-200 simultaneous users. Oh... and it >> never used to have this problem. This started 5 days ago. >> >> >> >> On Thursday, August 2, 2012 12:19:51 AM UTC-4, hyperflame wrote: >> >> > Just to be clear, the GAE datastore returns stale results ONLY at a >> > specific time, and only when load is low? Is it because of both of >> > those factors together or just a single one? Seems odd that GAE is >> > reacting slowly just when load is the lowest. Can you post some load >> > graphs? >> >> > If the staleness is due to low load, you could always run some fake >> > users to add to the load, then have your backend subtract those fake >> > users when it builds the scoreboards. It wouldn't be hard; you can >> > capture some real users data, save it to a log, then replay it against >> > production servers. >> >> > On Aug 1, 1:27 pm, Richard <[email protected]> wrote: >> > > Summary so far: >> >> > > "Sometimes" (at the same time of day.. when load is lowest), GAE will >> > do a >> > > put() and 5-10 seconds later when I do a query all to create >> > leaderboards >> > > for that game round, I get stale results..... for some of the entries. >> > > This is because the put() has completed, but not the (internal) >> > commit(). > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
