It seems to be fixed here, can you please make an announcement for us to
inform our customers our service is back ?
thanks by advance (and for your intervention)
On Tuesday, June 11, 2013 3:06:02 PM UTC+2, Thomas Tiercelin wrote:
since thursday it's very exhausting and frustrating to work with
cannot agree more, good luck for your debug ^^
On Tuesday, June 11, 2013 6:02:51 PM UTC+2, Ben Ritchie wrote:
Fair play..
Did you raise a ticket?
My apps not fully launched but this still sucks for my app to have
downtime because of this, Ive got enough bugs of my bloody own to cover up!
according to this thread
https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/TqKVL9TNq2A
the pb is solved, thanks !
On Tuesday, June 11, 2013 3:06:02 PM UTC+2, Thomas Tiercelin wrote:
since thursday it's very exhausting and frustrating to work with appengine
(6
Hi,
Just to confirm that there is an issue. We are experiencing a lot of
Deadline exception from times to times (but there is still a few everyday).
More information about it
here:
Same problem here, happening from time to time, including right now :-/
On Monday, June 10, 2013 2:40:30 PM UTC-4, Pertti Kellomäki wrote:
Hi Aaron,
Unfortunately I have no clue, the problem just went away by itself.
Probably some kind of transient failure.
Pertti
On Mon, Jun 10, 2013
same problem here, but it's not happening from time to time, its happening
very often and always since 2 hours
central auth is critical for us, please fix this ASAP definitely
Le jeudi 4 avril 2013 12:45:37 UTC+2, Pertti Kellomäki a écrit :
Hi,
I am accessing users' YouTube accounts using
Fair play..
Did you raise a ticket?
My apps not fully launched but this still sucks for my app to have downtime
because of this, Ive got enough bugs of my bloody own to cover up!
Haha
On Tuesday, 11 June 2013 14:06:02 UTC+1, Thomas Tiercelin wrote:
since thursday it's very exhausting and
Got confirmation on this SO comment [1] that Google is aware of the
situation and working on it.
[1]
http://stackoverflow.com/questions/17024282/how-to-avoid-failed-to-retrieve-access-token-error-invalid-grant-in/17027974?noredirect=1#comment24649419_17027974
On Tuesday, June 11, 2013 9:15:18
+1, this has caused my app to be down all day.
On Tuesday, June 11, 2013 1:05:14 PM UTC-4, Ronan Jouchet wrote:
Got confirmation on this SO comment [1] that Google is aware of the
situation and working on it.
[1]
star it here:
https://code.google.com/p/googleappengine/issues/detail?id=9476
On Tue, Jun 11, 2013 at 6:02 PM, Ben Ritchie benjamin.ritc...@gmail.comwrote:
Fair play..
Did you raise a ticket?
My apps not fully launched but this still sucks for my app to have
downtime because of this, Ive
Indeed we feel abandoned! All day our customers are calling because our GAE
software is down and there's nothing we can do... Looking at the support
packages;
https://cloud.google.com/support/packages
There should be at least a SLA with compensation clauses, we're losing
customers...
Op
Pertti,
I'm having this same problem. Did you figure out what the cause was?
On Thursday, April 4, 2013 6:45:37 AM UTC-4, Pertti Kellomäki wrote:
Hi,
I am accessing users' YouTube accounts using OAuth2Decorator in Python.
Access worked fine until yesterday, but today I'm getting this:
Hi Aaron,
Unfortunately I have no clue, the problem just went away by itself.
Probably some kind of transient failure.
Pertti
On Mon, Jun 10, 2013 at 7:56 PM, Aaron Sykes aaronpaulsy...@gmail.comwrote:
Pertti,
I'm having this same problem. Did you figure out what the cause was?
On
Hey Mustafa - if you're still experiencing this problem please file a
production ticket here...
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
Thank you.
-iein
On Sunday, May 13, 2012 3:14:09 PM UTC-7, Mustafa Paksoy wrote:
Hi,
Appengine deployment
Yup doing the same for me
On Aug 30, 10:37 am, Tom Saulpaugh t...@kintris.com wrote:
Just today we started getting this exception when writing to the
blobstore.
The API call file.Create() took too long to respond and was
cancelled.
Is anybody else getting these?
Thanks,
Tom
--
You
I've never had a problem with urlfetch to PayPal, but my usage is low
(10s of requests a month).
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this
Hi Jeff,
Sorry for the delayed reply. Since we have a seriously struck with
another problem in gql
which I already posted in
http://groups.google.com/group/google-appengine/browse_thread/thread/44f68399e1dea1c0/9b92b3a369f831d7?pli=1
I couldn't respond you.
My app id is os-dev. Its not deadline
Hi adhi,
Could you tell me the app ID for this application? When you mention
timeout errors, are these datastore timeouts or are they overall
deadline exceeded exceptions? It could be that fetching 1300 records
in one request does take longer than the allowed time for a datastore
operation.
Thankx nick...
i did it in batch of 25 entities at a time
i migrated using where clause in query
On Jun 4, 9:01 pm, Nick Johnson (Google) nick.john...@google.com
wrote:
Hi Ankur,
The easiest way to decrease your runtime is to decrease the number of round
trips. .fetch() on a query
Actually, even just fetching one entity by key will frequently cause a
Timeout. My logs are full of these...
On Apr 30, 2:59 pm, Sylvain sylvain.viv...@gmail.com wrote:
For my app, I never fetch more than 250 entities because I've seen
that if this values is bigger you raise too many datastore
Well, I've read a lot of posts about google datastore and the problems
with batch operations, relational approach to arrange data in bigtable
etc. but I always thought the problem wasn't in datastore itself but
in the way people use it. Now I can see with my experience that it
acts just in an
For my app, I never fetch more than 250 entities because I've seen
that if this values is bigger you raise too many datastore timeouts.
But even with 250 entities (with a very basic Kind) something I get a
timeout.
One funny thing is that you can fetch up to 1000 entities (whatever
kind, number
Today, my app has seen 2 timeout errors at 3:10 pm according to the
log. Each one was 30 seconds apart. One was a Get and the other a
Put. Each on totally different classes that are not connected in any
way.
On Apr 17, 4:15 pm, Brandon Thomson gra...@gmail.com wrote:
Google will not really
Hi,
I would just like to add myself into this, my app twitterautofollow (twollo)
regularly gets DataStore time outs on puts (in the most part). All my
entities are root entities.
I did have a thread open on this only a few days ago.
Paul
2009/4/17 Ray Malone rayish...@gmail.com
I'm seeing
Datastore timeout is one of the biggest (and oldest) issue with GAE
and mostly because it is random.
You can get it on get, put, fetch,... even with few entities.
I hope that soon, datastore timeout will be negligible. Currently, it
is not the case.
Regards
On 17 avr, 09:50, Paul Kinlan
Speaking only for my app, I can tell this is not an application
issue. My datastore is made up of only root entities and in most
cases works well quickly. My app doesn't see large volumes of
requests per second and it's more like requests per minute. There
is no possible way the errors I'm
Good for you that your company has good prospects. As somebody who has
built high traffic sites (co-founder of IGN.com), I offer some advice:
Don't even think about driving traffic to it unless it has been stable
for weeks. If you are having problems w/ minute traffic, you can't
imagine how bad
Google will not really acknowledge this as a problem or defect but
neither do they provide a lot of options for workaround. My experience
is that Timeouts do occur on about 0.5% of puts regardless of size of
entity. These are root entities. It is not caused by write contention
from multiple
On Thu, Apr 16, 2009 at 4:16 AM, DarkCoiote darkcoi...@gmail.com wrote:
On Apr 15, 3:26 pm, Jeff S (Google) j...@google.com wrote:
Hi Ray,
Which operation was is that timed out (get, query, put)? Also, how
consistently are you seeing these timeouts?
I generally recommend catching
Yes... I've read that...
The problem with using all entities as root is that I'm unable to use
transactions as it is... I would have to code a lit bit... although
I just found a paper describing a project that seems really good.
http://danielwilkerson.com/dist-trans-gae.html
I think it will be
I'm seeing random timeouts where there are many seconds or minutes
between requests and hours before app engine handled the same request
within 400ms. I hit another one today that will actually cost my
business, not much but some. My app needs to catch these and I am on
many pain points.
Hi Ray,
Which operation was is that timed out (get, query, put)? Also, how
consistently are you seeing these timeouts?
I generally recommend catching datastore timeouts and handling them in a way
that makes sense for your app. There are currently occasional (quite rare as
a percentage) timeouts
On 1 (one!!) single sign-on I got this error in my log. Several
people login during the day and than no error appears, so why this
suddenly happens is a big mistery!!
The update is only on these fields:
r[0].update_record(last_attempt_time=int(now),
last_login_time=now2.strftime(%Y-%m-%d
Are you seeing timeouts with get_by_key_name consistently with a
particular model, or randomly?
On Dec 21, 2:56 am, Guy Rutenberg g...@labpixies.com wrote:
Hi,
I've a strange problem, I've a request that only calls get_by_key_name
(one time) and does no further work with the Datastore.
It's laready has been reported here:
http://groups.google.com/group/google-appengine/browse_thread/thread/826c4be4a59cbfa
--
Alex
http://sharp-developer.net/
On Dec 8, 9:55 pm, m1ck [EMAIL PROTECTED] wrote:
why am i getting a Timeout Exception when Accessing the datastore
Exception Type:
I am also. Just single put operation somtimes caused 'datastore
timeout: operation took too long.'
- my application id : lifography
My application doesn't exceed to any quota. (1%)
One of this error was occured at Nov 26,2008 AM 12:06 (PST).
File
I seem to be getting unusual timeouts too... www.bigbikemap.com
On Nov 26, 8:28 am, ksjun [EMAIL PROTECTED] wrote:
I am also. Just single put operation somtimes caused 'datastore
timeout: operation took too long.'
- my application id : lifography
My application doesn't exceed to any quota.
I am as well. Single put of simple record in database with less than
100 objects total. Makes me very concerned about viability of
platform.
On Nov 26, 10:39 am, Fred [EMAIL PROTECTED] wrote:
I seem to be getting unusual timeouts too...www.bigbikemap.com
On Nov 26, 8:28 am, ksjun [EMAIL
I am also seeing a lot of time spent in WAIT? Sometimes as much as 3/4
of total CPU for any given set of calls! Has the datastore latency
issue mentioned above been resolved?
Here is an example from a profile run:
ncalls tottime percall cumtime percall filename:lineno(function)
Jeff,
I am fetching 100 records on one go. The funny thing is, the query works 20%
of the time and fails 80% of the time.
no consistency and as the volume of data increase, it fails even more :(
I have 2 million records to upload and have stopped at 700K because of
scaling / time-out issues.
How can we help for this ?
Each day, I've several Timeout.
Do you still need more info about it (date,time, app_id,...) ?
Regards
On 30 sep, 18:57, johnP [EMAIL PROTECTED] wrote:
For a while today, I started seeing errors in custom form validation.
Requesting self.instance in ModelForm form
I've been seeing Timeouts on data put operations about 30-80 times a
day (which accounts for as much as 1-3% of all write requests) ever
since my app went into production on August 18. This is happening
every day and it's very annoying. It's worse during some periods,
(e.g. when the GAE team
For a while today, I started seeing errors in custom form validation.
Requesting self.instance in ModelForm form resulted in ValueErrors.
Now, it seems to have recovered a bit...
On Sep 30, 9:43 am, Adam Loving [EMAIL PROTECTED] wrote:
I am seeing the datastore timeout error
Hi,
I don't know how much work has been done on this front, but my app is
still cripple by this issue.
Maybe the amount of timeout errors in the log has decrease a little,
but so has the amount of happy users of my site =(
/ronald
On Sep 19, 9:45 pm, Marzia Niccolai [EMAIL PROTECTED] wrote:
Hi,
Brett wrote on Sept 16 (http://groups.google.com/group/google-
appengine-downtime-notify/browse_thread/thread/3a61e15fee584734) that
the issue has been addressed and Datastore writes where back to
normal,
but I'm still seeing about 30 entries a day in my log file with the by-
now-much-dreaded
Hi,
Our engineers are looking in to your reports.
If all of the people experiencing quota issues like this could email me
directly with your application id, as well as the approximate times these
errors were occurring, that would be helpful!
Thanks,
Marzia
On Fri, Sep 19, 2008 at 11:17 AM,
FYI - I'm also starting to see these error messages come up today
while doing simple put calls.
On Sep 10, 1:32 pm, Marzia Niccolai [EMAIL PROTECTED] wrote:
Hi,
Our engineering team is currently investigating increased datastore latency
from earlier today. More details will be posted in the
Hi,
Our engineering team is currently investigating increased datastore latency
from earlier today. More details will be posted in the downtime-notify
group.
-Marzia
On Wed, Sep 10, 2008 at 1:16 PM, Ronald [EMAIL PROTECTED] wrote:
Hi,
I'm seeing a number of Timeout errors on my log file:
48 matches
Mail list logo
