Trying to delete them manually is certainly worth attempting; since it
appears to be the same objects, it may be possible to get past this. I'll
also try wrapping it in a transaction but, like you, I can't see why it
should make a difference.
--
You received this message because you are
By what you wrote, I assume you're referring to the query speed, not the
speed of the deletion. I presume that deleting an object or collection of
object requires a time that's independent of other factors in the
datastore; that is, once I know the object's key, deleting it takes an
Yeah, if you're doing a delete by previously-known key I would expect
constant time operation. I have no idea what might be causing your
issue, sorry.
Jeff
On Sun, Dec 11, 2011 at 4:26 PM, Michael michael.ol...@gmail.com wrote:
By what you wrote, I assume you're referring to the query speed,
We switched to High Replication last night (details will be in another
post) and in the last almost 24 hours we've received 356 warnings in the
logs:
Request was aborted after waiting too long to attempt to service your request.
This may happen sporadically when the App Engine serving cluster
I went through a Master/Slave - High Replication migration over the
weekend and it didn't go well. Hoping I can get some info on if we did
anything wrong but mostly wanted to relay the experience for others.
I did a couple of test migrations the week before, running the migration
tool through
Hi, I am trying to make some application for google app engine.
I am trying to get data from this url
http://streamerapi.finance.yahoo.com/s treamer/1.0?
s=EURUSD=Xk=l10,t10,g00,h00,v00,j10callback=parent.yfs_u1fmktmcb=parent.yfs_mktmc
bgencallback= parent.yfs_gencbr=0
The problem is that
Hi App Engine Team,
I've started getting random 500 responses with Request was aborted after
waiting too long to attempt to service your request. This may happen
sporadically when the App Engine serving cluster is under unexpectedly high
or uneven load. If you see this message frequently,
After signing in, connecting to the cloud, and pressing the Say
Hello in the emulator (2.2), the emulator returns and just hangs with
message, Contacting Server, but never returns with the expected
round-trip message, Hello, my-email, This is in debug mode
as Local App Engine Connected
Hi,
I am trying to deploy a java web application to google app engine as
per http://code.google.com/eclipse/docs/getting_started.html
When i try to signin to google using eclipse i get the following
exception
Could not sign in. Check that your computer's date and time are
correct; sign-in
I've been able to setup Eclipse with the GE plug-in, install the
Android SDK, and load them into Eclipse. When I run in debug mode and
launch the (2.2) emulator, I press the Say Hello button to test the
roundtrip message but I do *not*get the return message including my
email. I've been trying to
Hi App Engine Team,
I wanted to add more info for this issue.
My App is in Development. I am experiencing this issue when there is no
load. (max 2 concurrent requests and I see there are 3 live instances).
Over the past 24 hours I got this error for ~8% of the requests.
This is not the first
On Sat, Dec 10, 2011 at 6:26 AM, BoulderGae sc...@scmlabs.com wrote:
The user service will always return null when cron is calling. The
way to tell that cron is calling is to check for the X-AppEngine-
Cron header. It is set by the cron service and is stripped from all
other calls to your
W
Sent from my BlackBerry® smartphone provided by Airtel Nigeria.
-Original Message-
From: buzzjourney l...@buzzjourney.com
Sender: google-appengine-java@googlegroups.com
Date: Sun, 11 Dec 2011 22:21:27
To: google-appengine-java@googlegroups.com
Reply-To:
13 matches
Mail list logo
