Thanks Ryan.
It works.
Do you know where this is documented in GAE ?
On Mon, Aug 24, 2015 at 6:58 AM, Ryan (Cloud Platform Support) <
rbruy...@google.com> wrote:
> Salutations James,
>
> You need to run 'blobstore.create_gs_key' then pass the results to the
> get_serving_url.
>
> self.response.
Alex,
Basically, GAE had a price increase by making shared memcache unusable.
You have to signup for the premium memcache at 12 cents a GB-hour to get
back to the way it use to work.
This was dishonest of GAE and they have not even announced that they
essentially deprecated the shared memcache s
I am using about 30 megs of memory cache for 1200 items -- not very much
imo. In the past I have used as much as 100 megs without seeing excessive
purges.
Hard to code against parameters which are not documented and possibly even
change based on unknown factors.
At this point, you can even assum
Brian,
The UI is good. The problem is that transactions are not completing.
When the first ACH debit to my checking account was declined on August 8th,
after working for months, I called the bank. They told me that no such ACH
debit was presented to them and they declined nothing. The message
Wolfram --
Thank you for the response.
I will do as you suggest ... access the stale group with a GET to clear up
the stale replica.
Also, in rare cases, we have seen a get for a single row in the datastore,
return an old result and the current result randomly, many days after the
item was upda
I agree ... the problem was fixed around 3pm yesterday as far as I know.
It kind of freaked us out ... one of the biggest outages we have ever seen
with GAE, about 5 hours I think.
Thanks so much
On Fri, Jun 21, 2013 at 1:49 PM, John Lowry wrote:
> Jared,
>
> I have again verified that the pro
another puzzling thing about this query ...
it is only really slow when the offset is 0 (or a very low value)
it runs less a second when the offset is larger, like 1000
is there something strange when you are trying to find the most recent
blobs created, even if the creation happened hours (or d
There is nothing failing ... I guess the good news is the jobs showing as
active are not really running
I tried to delete the entire datastore to duplicate what i can do on the
GoogleAppEngineLauncher via info (clear datastore on launch)
the datastore appears to be deleted but _AE_DatastoreAdmin_
