[google-appengine] AppEngine Application Problem

[Gnani Chaitanya]

Hi When I am trying to open the aggregate url then I am getting below the 
error, presently I am using free version and my data usage is within the 
limit.

A problem has occurred that prevents your AppEngine application from 
responding. Your application may have exceeded its per-minute or daily 
usage quotas.

Please visit your application dashboard at *Google AppEngine* 
. The *Billing Status* section will indicate 
what daily or per-minute usage limits your application has exceeded.

If your application's usage limits have not been exceeded, then look for 
performance issues within Google AppEngine cloud services. From your 
application dashboard, click on the the *System Status* link on the left 
sidebar under the *Resources* heading. This will report problems with 
Google AppEngine cloud services.

If neither of those indicate any problems, then your application's Logs 
may; these are reachable from the dashboard via the *Logs* link on the left 
sidebar under the *Main* heading.


I am unable to find the erroe Please suggest me.


Rgds,

Chaitanya.D

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/79b91657-0baf-43fb-9e91-0a50c21fa1f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Why can’t transactional tasks be named?

[Nickolas Daskalou]

Hi Kim,

Could we add a list of exceptions allowed to be thrown by the Task Queue
service and still consider the transaction as successful?

E.g. (mostly stolen from here

)

from google.appengine.api import taskqueue
from google.appengine.ext import ndb

@ndb.transactional
def do_something_in_transaction():
  taskqueue.add(url='/path/to/my/worker', transactional=True,
allow_transactional_exceptions=[taskqueue.TaskAlreadyExistsError,
taskqueue.TombstonedTaskError])

  #...

do_something_in_transaction()


Nick


On 29 April 2016 at 09:18, 'Kim Lewandowski' via Google App Engine <
google-appengine@googlegroups.com> wrote:

> Hi Jeff,
>
> if we allowed named tasks then the transactional task could be rejected
> because the task name already exists.
>
> "Task Name 1"  -> Datastore transaction -> AddTask to Queue
> "Task Name 1" -> Datastore transaction (???) -> 
>
>
> On Wednesday, April 27, 2016 at 12:43:43 PM UTC-7, Jeff Schnitzer wrote:
>>
>> My task queues sometimes have a lot of tasks sitting in them for various
>> reasons (usually failing/retrying). I’d _really_ love to be able to look at
>> a queue at a glance and see what’s in it. Instead it’s a wall of numbers.
>>
>> Ah hah! I can name tasks, and this will show up in the interface, right?
>>
>> I just tried that and get “transactional tasks cannot be named”. What’s
>> the rationale for this? I get that the task name needs to be unique, but
>> that can be fixed with a suffix…
>>
>> This was asked in a SO question but the answer, although accepted, is
>> bogus.
>>
>> Any ideas?
>>
>> Thanks,
>> Jeff
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/9970005d-cdd1-4d78-bf71-a2da58d1a465%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAOj3zuCcaBJFMN7KNEV_jW361v5Zwm4Z7X0oM9bqh9fFNvswQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unwelcome change: Paginating the task queue list

[Christian F. Howes]

Kim,

what's the release cycle for the console?  is the next release or 2 
measured in days, weeks, or months?  this change really slows down our 
workflow and increases our costs to manage the platform.  it's quite sad 
that we keep eroding one of the biggest features of GAE - simple 
management, by making changes like this.

Thanks,

Christian


On Thursday, April 28, 2016 at 1:37:14 PM UTC-7, Kim Lewandowski wrote:
>
> Hi Everyone,
>
> Thanks for the feedback. I've submitted a bug to get this increased to 100 
> queues/tasks per page. The fix should go out in the next release or 2.
>
> Also, I'm gathering requirements on making the Task Queues and Cron UI 
> even better. If you have more feedback to share, please email it to me! 
> lil...@google.com 
>
> -Kim Lewandowski
> App Engine, Product Manager
>
> On Thursday, April 28, 2016 at 9:15:42 AM UTC-7, Jeff Schnitzer wrote:
>>
>> Hi Google…
>>
>> Yesterday I noticed that the “task queue” viewer in the cloud console was 
>> changed to paginate the results every 10 entries. I can no longer see the 
>> state of all my queues at a glance. Constantly clicking through four pages 
>> is irksome, especially when there is a vast sea of blank space on my nice 
>> tall monitor.
>>
>> My app performs a lot of orchestration based on task queues; checking to 
>> see if any of the jobs are backed up is part of our standard measurement of 
>> the general health of the system. This just got a lot more painful.
>>
>> If you have to paginate, please make the list hundreds long. Not 10. I 
>> heard my entire team scream in agony, one at a time, as they noticed the 
>> change :-(
>>
>> Thanks,
>> Jeff
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cd5ff1b9-def0-4955-80fa-68e27c672f96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Why can’t transactional tasks be named?

['Kim Lewandowski' via Google App Engine]

Hi Jeff,

if we allowed named tasks then the transactional task could be rejected 
because the task name already exists.

"Task Name 1"  -> Datastore transaction -> AddTask to Queue
"Task Name 1" -> Datastore transaction (???) -> 


On Wednesday, April 27, 2016 at 12:43:43 PM UTC-7, Jeff Schnitzer wrote:
>
> My task queues sometimes have a lot of tasks sitting in them for various 
> reasons (usually failing/retrying). I’d _really_ love to be able to look at 
> a queue at a glance and see what’s in it. Instead it’s a wall of numbers.
>
> Ah hah! I can name tasks, and this will show up in the interface, right?
>
> I just tried that and get “transactional tasks cannot be named”. What’s 
> the rationale for this? I get that the task name needs to be unique, but 
> that can be fixed with a suffix…
>
> This was asked in a SO question but the answer, although accepted, is 
> bogus.
>
> Any ideas?
>
> Thanks,
> Jeff
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9970005d-cdd1-4d78-bf71-a2da58d1a465%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] What is the actual maximum number of versions?

[Kevin Liu]

https://cloud.google.com/appengine/docs/python/tools/uploadinganapp
>
> *Important:* App Engine has a limit of 10 deployed versions per 
> application. If you try to deploy an 11th version you'll get an error: "Too 
> Many Versions (403)." You can use the Cloud Platform Console to delete an 
> older version and then upload your latest code.


Whereas if you look at 
https://cloud.google.com/appengine/docs/php/an-overview-of-app-engine#limits 
It says that the maximum versions for a free app is 15, and 120 for a paid 
app. 

Both documentation pages say: "Last updated April 27, 2016."

*So which is it?*

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/abc1e289-19f0-459d-af0b-14f28e29b5f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Push queues: No. of running tasks < No. of tasks in queue < Max number of concurrent tasks

['Kim Lewandowski' via Google App Engine]

Hi Manni,

It sounds like 1 of 2 things is happening:

1. Queue depth is not accurate. We are actively working on improving the 
accuracy of this number (it's a really hard problem to solve!)
2. You may have tasks scheduled to run in the future (either intentionally 
or because they are being retried)

If you want to email me your application ID and queue name, we could dig in 
and see what's going on. lil...@google.com

-Kim
App Engine, Product Manager

On Thursday, April 28, 2016 at 10:45:49 AM UTC-7, Manuele Cavalli-Sforza 
wrote:
>
> I have a push queue with a number of long running tasks enqueued. I notice 
> that the push queue has reached a state, however, where the No. of running 
> tasks < No. of tasks in queue < Max number of concurrent tasks. 
>
> This is unideal, as I would like the queue to be processing at its maximum 
> capacity. Does this have to do with the bucket size set on the queue? Would 
> tweaking this alter the queue's responsiveness? 
>
> It is also relevant to note that I updated the queue configuration, after 
> adding the tasks, to be a max of 40 concurrent tasks. Also, I added the 
> tasks all at the same time. I noticed that the queue initially processed 
> the tasks well at the original 20 concurrent task limit, but -- when 
> updated to 40 concurrent tasks -- did not seem to respond, and always kept 
> a task running number of under 20. Any insights from other users' 
> experience or the Google team? 
>
> Thanks,
>
> Manni
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/487e706e-e5ee-4a4d-92d6-c82039edd909%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Standard Env built-in libs docs missing

['Zeehad (Cloud Platform Support)' via Google App Engine]

Hello Brian,

Thanks for reporting the error in the documentation. This has been reported 
internally and should be fixed soon. You can also directly submit feedback 
by clicking 'Send feedback' from the top right corner of the page 
containing the documentation error.

Cheers!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b85413da-c690-4626-bdfd-b1a2b5ddbc00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Multiple AppEngine 104 errors

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Alexandru & Ice13ill,

These error codes represent several different issues. 

500 means an internal server error, which is not specific enough to 
determine a cause unless you check the logs of your app / server. 

404 means a resource was requested but not found, most often since no 
request handler is configured for the route requested.

104 is an App Engine error code used when concurrent requests are not 
configured on your app 
 
(threadsafe is false in app.yaml or appengine-web.xml) 

Finally, ConcurrentModificationExceptioYou can read about how to avoid this 
in the documentationn is an error relating to the concurrent modification 
of a Datastore entity group too often in a given timeframe. You can read 
about how to avoid this in the documentation [1] 
, [2] 
.

If you could post the full stack traces / error logs, this would greatly 
increase anybody's ability to determine what was happening.

Now that the issues have resolved, it's possible that it may simply be 
beyond anyone to try to determine what's happening. Feel free to ask any 
questions you may have, I'll be happy to help.

Sincerely,

Nick
Cloud Platform Community Support

On Thursday, April 28, 2016 at 6:06:08 AM UTC-4, Alexandru Farcaş wrote:
>
> Hi,
>
> I have multiple errors with error code 104. I have this behaviour since 
> 11:50am EEST. 
> I receive a lot of errors at task creation. I receive this errors but the 
> tasks are still created in task queue!
>
> java.util.ConcurrentModificationException >> too much contention on these 
>> datastore entities. please try again.
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/35196a3b-0484-412a-a8e4-2cd0b4ffae09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Unwelcome change: Paginating the task queue list

['Kim Lewandowski' via Google App Engine]

Hi Everyone,

Thanks for the feedback. I've submitted a bug to get this increased to 100 
queues/tasks per page. The fix should go out in the next release or 2.

Also, I'm gathering requirements on making the Task Queues and Cron UI even 
better. If you have more feedback to share, please email it to me! 
lil...@google.com

-Kim Lewandowski
App Engine, Product Manager

On Thursday, April 28, 2016 at 9:15:42 AM UTC-7, Jeff Schnitzer wrote:
>
> Hi Google…
>
> Yesterday I noticed that the “task queue” viewer in the cloud console was 
> changed to paginate the results every 10 entries. I can no longer see the 
> state of all my queues at a glance. Constantly clicking through four pages 
> is irksome, especially when there is a vast sea of blank space on my nice 
> tall monitor.
>
> My app performs a lot of orchestration based on task queues; checking to 
> see if any of the jobs are backed up is part of our standard measurement of 
> the general health of the system. This just got a lot more painful.
>
> If you have to paginate, please make the list hundreds long. Not 10. I 
> heard my entire team scream in agony, one at a time, as they noticed the 
> change :-(
>
> Thanks,
> Jeff
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c3092f73-3823-42be-ad7c-fbf564734dd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Unwelcome change: Paginating the task queue list

[George-Cristian Bîrzan]

There's no issue about this, but I also hate it. I don't mind task
pagination, but this is insane. At least make the page size something like
25+. We have 14 and it's annoying, I cannot imagine how bad it is for
people with more...

On 28 April 2016 at 23:13, Kaan Soral  wrote:

> +1
>
> Not that I use/can-use the console anymore
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/b0e48266-e425-4839-8c3c-4ba9f262f438%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
George-Cristian Bîrzan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CA%2B3w0iXResFv6RcbmBzu9hxD%2B-7kY-vDb4oSHwaBktE5UWNpPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: dev_appserver.py on Windows won't shut down properly

[Bartholomew Furrow]

Adam,

Thanks a lot for following up with me again, especially on a problem that
isn't intrinsic to App Engine. It sounds like there isn't a perfect
solution, and I really appreciate you explaining what the challenges are.

Since I've spent a bunch of time on this as well, I'll include a couple
more musings for people who find this thread later down the road. Some of
it, like your response, may be generally useful cygwin/bash stuff. Please
feel free to ignore the rest of this email. :-)

Bartholomew

- Running dev_appserver.py in a .sh file in Cygwin spawns the following
processes: bash.exe; python.exe (with bash.exe as its parent); python.exe
(with the other python.exe as its parent). To be clear, the bash.exe
process is spawned when your script hits the line "$pypath/python.exe
$gaepath/dev_appserver.py ...", and it's in addition to whatever shell
you're running. You can't use 'wait' or 'kill' on either python process
because they aren't considered to belong to the bash shell running
python.exe, and not the one running your script.

- To find out the PID of the bash.exe that's spawned to run, you can do
something like this:
$pypath/python.exe $gaepath\\dev_appserver.py \
--skip_sdk_update_check=yes --port=$port --admin_port=$admin_port
app/app.yaml
& echo $!
wait

- If you want to do something with the output of dev_appserver.py, like run
it through grep -v so you don't see a bunch of spam, you can do something
like this:
pid_file=`mktemp`
$pypath/python.exe $gaepath\\dev_appserver.py \
--skip_sdk_update_check=yes --port=$port --admin_port=$admin_port
app/app.yaml
& echo $! >&4) 4>$pid_file 3>&1 1>&2 2>&3 3>&- |
grep -vE "recording.py|module.py:787.*GET /([^a]|a[^/]).*(304|200)"
3>&1 1>&2 2>&3 3>&-

This says: "In a shell, run dev_appserver in the background, and echo the
process ID into stream 4. Take the output of that shell (now in streams 1,
2 and 4). Put stream 4 into $pid_file. Swap stdout with stderr (that's 3>&1
1>&2 2>&3 3>&-). Grep out all requests (formerly appearing in stderr) for
static files and all appstats information. Swap stdout with stderr again.

- To find out the python processes, you can then run commands like:
bashpid=`cat $pid_file`
pypid1=`wmic process where (parentprocessid=$bashpid) get processid`
pypid2=`wmic process where (parentprocessid=$pypid1) get processid`

- To wait for a process to terminate when *wait* isn't an option, you can
use a command like:
while [ -e /proc/$pid ]; do sleep 0.5; done;

- Even if you trap sigint, for some reason cygwin immediately passes it on
to the process. So something like:
trap kill_all_jobs sigint
function kill_all_jobs() {
  taskkill /pid $bashpid /f /t
}
...won't work, because $bashpid died the second you hit ctrl+c. It even
took $pypid1 with it, but not $pypid2. You could, however, put this in
kill_all_jobs:
taskkill /pid $pypid2 /f /t
...and that will complete the cleanup, though without the smooth shutdown.
I don't know how to make the smooth shutdown happen on cygwin with ctrl+c
because I don't know how to avoid the bash.exe and pypid1 processes being
shut down before the trigger hits.

On Tue, Apr 26, 2016 at 1:45 PM 'Adam (Cloud Platform Support)' via Google
App Engine  wrote:

> This relates to a known issue with the development server on Windows: It
> relies on KeyboardInterrupt to shutdown cleanly, as there is no equivalent
> to POSIX SIGINT on Windows (see here
> , here
>  and
> here 
> for some referenced public issues). Even if you use 'kill -SIGINT ' in
> Cywin, the 'SIGINT' doesn't translate to native Windows processes.
>
> One thing you could try is to install Python using the Cygwin installer
> (run from /usr/bin/python) and install the App Engine Python SDK for Linux
> / other platforms inside of your Cygwin environment.
>
> If that doesn't work, another more involved and hacky option would be to
> call google.appengine.tools.devappserver2.api_server.cleanup_stubs() from
> your own handler in your application (eg. do 'curl
> http://localhost:8080/cleanup_stubs_handler' immediately before killing
> the process).
>
> I haven't tested any of this myself, so take this information with a grain
> of salt.
>
> On Monday, April 25, 2016 at 12:29:08 AM UTC-4, Bartholomew Furrow wrote:
>>
>> Adam,
>>
>> That works for cmd.exe! FYI, python.exe wasn't working for me when I sent
>> that message, but I apparently overwrote it with a 0B file; once restored,
>> it did what you said. The command I listed above (sans *w*) works in
>> cmd.exe and in a batch file run from cmd.exe. Thank you for pointing out my
>> problem!
>>
>> My next challenge, if you're willing to keep diving into madness with me,
>> is how to make this work from cygwin. If I run the cygwin command I pasted
>> above (with python.exe rather than pythonw.exe):
>> 1. 

Re: [google-appengine] Unwelcome change: Paginating the task queue list

[Kaan Soral]

+1

Not that I use/can-use the console anymore

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b0e48266-e425-4839-8c3c-4ba9f262f438%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Push queues: No. of running tasks < No. of tasks in queue < Max number of concurrent tasks

[Kaan Soral]

It could be instance related, if your instances are not aggressive, it 
might occur

If tasks use too much memory etc., it might be hard to run them, my .02

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/256f5bd5-1446-40c4-a0f7-6e21436de479%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: mounting nfs on google app engine

[pankaj kumar]

It seems aws does not support it 
either: 
https://webcache.googleusercontent.com/search?q=cache:9c6QEoKcS3gJ:https://forums.aws.amazon.com/thread.jspa%3FthreadID%3D177850+&cd=1&hl=en&ct=clnk&gl=us

Is it possible to change some code somewhere in the sdk to enable 
--net=host? Or is it possible to access the host machine in a clean way to 
run some commands and create a virtual ethernet adapter and link it to the 
docker instance?

Thanks


On Wednesday, April 27, 2016 at 10:00:00 PM UTC-7, pankaj kumar wrote:
>
> Docker has this --net=host parameter which will enable host networking. 
> The container gets ip address same as the host. Can we have that in the 
> google app engine? That way services like nfs on the same network that need 
> to connect to the client can be utilized in the container. 
>
> On Wednesday, April 27, 2016 at 6:33:48 PM UTC-7, pankaj kumar wrote:
>>
>> I am trying to mount a nfs share onto a app engine container. Everything 
>> seems to work other than the fact that the container has a 172.* ip address 
>> and the default network is a 10.* ip address. Is there a way to set 
>> networking in the containers to get the same 10.* ip address? (Bridged vs 
>> nat or something?)
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c0e856b7-cd03-4c47-ad70-742cb66a68c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Push queues: No. of running tasks < No. of tasks in queue < Max number of concurrent tasks

[Manuele Cavalli-Sforza]

Attempted to tweak batch_size and rate since posting and have not seen 
differences.

On Thursday, April 28, 2016 at 1:45:49 PM UTC-4, Manuele Cavalli-Sforza 
wrote:
>
> I have a push queue with a number of long running tasks enqueued. I notice 
> that the push queue has reached a state, however, where the No. of running 
> tasks < No. of tasks in queue < Max number of concurrent tasks. 
>
> This is unideal, as I would like the queue to be processing at its maximum 
> capacity. Does this have to do with the bucket size set on the queue? Would 
> tweaking this alter the queue's responsiveness? 
>
> It is also relevant to note that I updated the queue configuration, after 
> adding the tasks, to be a max of 40 concurrent tasks. Also, I added the 
> tasks all at the same time. I noticed that the queue initially processed 
> the tasks well at the original 20 concurrent task limit, but -- when 
> updated to 40 concurrent tasks -- did not seem to respond, and always kept 
> a task running number of under 20. Any insights from other users' 
> experience or the Google team? 
>
> Thanks,
>
> Manni
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b1f1637d-3b5c-4429-9eed-00b01bc3436b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Push queues: No. of running tasks < No. of tasks in queue < Max number of concurrent tasks

[Manuele Cavalli-Sforza]

I have a push queue with a number of long running tasks enqueued. I notice 
that the push queue has reached a state, however, where the No. of running 
tasks < No. of tasks in queue < Max number of concurrent tasks. 

This is unideal, as I would like the queue to be processing at its maximum 
capacity. Does this have to do with the bucket size set on the queue? Would 
tweaking this alter the queue's responsiveness? 

It is also relevant to note that I updated the queue configuration, after 
adding the tasks, to be a max of 40 concurrent tasks. Also, I added the 
tasks all at the same time. I noticed that the queue initially processed 
the tasks well at the original 20 concurrent task limit, but -- when 
updated to 40 concurrent tasks -- did not seem to respond, and always kept 
a task running number of under 20. Any insights from other users' 
experience or the Google team? 

Thanks,

Manni

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1eb73db2-0afd-4862-afe0-a9690d7acd34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Error while calling endpoint with JS Library (A network error occurred, and the request could not be completed.)

['Nicholas (Google Cloud Support)' via Google App Engine]

Thanks for posting your issue here and providing some context. It's 
difficult to know exactly what the error is, especially if it's transient.

>From what I understand, the client is making requests to your Cloud 
Endpoints using the API Client Library for Javascript. If this is the case, 
the generic way of issuing such requests is using the 
gapi.client.request(args) 

 
method. This returns a promise with which to use the then() or execute() 
methods.

Unfortunately, the documentation 

 
for both those methods does not state explicitly under what conditions it 
would return the values you received. From this, it's fair to suspect those 
values are actually returned from the server and not an issue with the 
Javascript API. This could be confirmed by inspecting the network requests 
using Chrome Developer Tools 
 and 
looking at the raw response.

That being said, if it's confirmed to be a response from the server and is 
reproducible, please feel free provide the Endpoints code that causes this 
so we can attempt to reproduce and identify the root cause. Also, please 
test this endpoint using the API Explorer. If it's very rare, I would 
suggest adding some retry system to your front end to account for network 
issues like this. An example follows:

var request_args = {
  'params': {
'q': 'search_values'
  },
  'path': 'path/to/resource'
};


function success(response) {}
function failure(reason) {
  console.error(reason);
}


var promise = gapi.client.request(request_args).then(success, function (
reason) {
  failure(reason);
  console.debug('retrying');
  setTimeout(function () {
gapi.client.request(request_args).then(success, failure);
  }, 500);
});


Hope this helps. Let us know if you continue to experience this network 
error and can confirm it's a platform issue or if you have any other 
questions on the subject.

On Wednesday, April 27, 2016 at 3:43:17 PM UTC-4, Renaud Tarnec wrote:
>
> Hello,
>
> Today, after calling one of my Endpoints from a web page through the 
> JavaScript API I got the following values for the response from the API:
>
> resp.code: -1
>
> resp.message:  A network error occurred, and the request could not be 
> completed.
>
> This endpoint saves an entity in the Datastore with Objectify and adds a 
> Task to a Queue (all within an Objectify transaction). Actually the code 
> was executed correctly, despite the error message (i.e. the entity was 
> saved in the Datastore and the task executed correctly).
>
> It's the first time I encounter this error, and its several months I work 
> on this application. Right after I was able to call the API the same way 
> without anymore problems.
>
> Any explanations or recommendations?
>
> Many thanks in advance
> Renaud
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/1310a7c8-dfda-4fcd-9ac1-87b890284cc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Multiple AppEngine 104 errors

[Ice13ill]

After a while, it seams everything went back to normal, but I think there 
were 60-70 minutes with severe impact on request handling.
Because of 104, 404, 500 errors, many tasks could not be executed and a 
very high retry rate caused high latencies and lots of spawned instances.

It's very strange that nobody else seamed to had this issue and also, 
nobody from google sent an email or reply to this thread.

On Thursday, April 28, 2016 at 1:43:15 PM UTC+3, Alexandru Farcaş wrote:
>
> In the last 20 minutes I didn't received 104 errors and the tasks were 
> created with success! 
> It seems that the application is running as it used to run ..
>
> On Thursday, April 28, 2016 at 1:17:43 PM UTC+3, Ice13ill wrote:
>>
>> Same for me.
>> Also, many 500 and 404 errors and very high latencies.
>>
>> On Thursday, April 28, 2016 at 1:06:08 PM UTC+3, Alexandru Farcaş wrote:
>>>
>>> Hi,
>>>
>>> I have multiple errors with error code 104. I have this behaviour since 
>>> 11:50am EEST. 
>>> I receive a lot of errors at task creation. I receive this errors but 
>>> the tasks are still created in task queue!
>>>
>>> java.util.ConcurrentModificationException >> too much contention on 
 these datastore entities. please try again.
>>>
>>>
>>>  
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fe9dd608-2344-482b-896a-2d769e795854%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Unwelcome change: Paginating the task queue list

[PK]

Agree

PK
p...@gae123.com




> On Apr 28, 2016, at 9:16 AM, Stefano Ciccarelli 
>  wrote:
> 
> I'm about to write the kind of post I hate: +1!
> 
> Il giorno gio 28 apr 2016 alle ore 18:15 Jeff Schnitzer  > ha scritto:
> Hi Google…
> 
> Yesterday I noticed that the “task queue” viewer in the cloud console was 
> changed to paginate the results every 10 entries. I can no longer see the 
> state of all my queues at a glance. Constantly clicking through four pages is 
> irksome, especially when there is a vast sea of blank space on my nice tall 
> monitor.
> 
> My app performs a lot of orchestration based on task queues; checking to see 
> if any of the jobs are backed up is part of our standard measurement of the 
> general health of the system. This just got a lot more painful.
> 
> If you have to paginate, please make the list hundreds long. Not 10. I heard 
> my entire team scream in agony, one at a time, as they noticed the change :-(
> 
> Thanks,
> Jeff
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/CADK-0ujKTUv%2BRm6g5y7NzAqkyCYpFdqrmUS-Cj9FGqY5G%3D-sVQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> -- 
> Stefano Ciccarelli 
> GAE Application Division 
> / Director 
> stefano.ciccare...@mmbsoftware.it  
> 
> M.M.B. s.r.l. 
> via Granarolo, 177/7 - 48018 Faenza (RA) - Italy 
> tel. +39.0546.637711 - fax +39.0546.46077 
> www.mmbsoftware.it  - i...@mmbsoftware.it 
> 
> Le informazioni contenute in questa comunicazione sono riservate e destinate 
> esclusivamente alla/e persona/e o all'ente sopra indicati. E' vietato ai 
> soggetti diversi dai destinatari qualsiasi uso, copia, diffusione di quanto 
> in esso contenuto sia ai sensi dell'art. 616 c.p., sia ai sensi del DL n. 
> 196/03. Se questa comunicazione Vi e' pervenuta per errore, Vi preghiamo di 
> rispondere a questa e-mail e successivamente cancellarla dal Vostro sistema.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/CAArRkeXu%3DRFSZecehCkR6m1-MadaPBDVxAOoRS3BA_pnrCL_sQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/155D6A5E-594E-4BFB-92FC-BE0BC1538382%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Unwelcome change: Paginating the task queue list

[Stefano Ciccarelli]

I'm about to write the kind of post I hate: +1!

Il giorno gio 28 apr 2016 alle ore 18:15 Jeff Schnitzer 
ha scritto:

> Hi Google…
>
> Yesterday I noticed that the “task queue” viewer in the cloud console was
> changed to paginate the results every 10 entries. I can no longer see the
> state of all my queues at a glance. Constantly clicking through four pages
> is irksome, especially when there is a vast sea of blank space on my nice
> tall monitor.
>
> My app performs a lot of orchestration based on task queues; checking to
> see if any of the jobs are backed up is part of our standard measurement of
> the general health of the system. This just got a lot more painful.
>
> If you have to paginate, please make the list hundreds long. Not 10. I
> heard my entire team scream in agony, one at a time, as they noticed the
> change :-(
>
> Thanks,
> Jeff
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/CADK-0ujKTUv%2BRm6g5y7NzAqkyCYpFdqrmUS-Cj9FGqY5G%3D-sVQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Stefano Ciccarelli*
GAE Application Division
/ Director
stefano.ciccare...@mmbsoftware.it

*M.M.B. s.r.l.*
via Granarolo, 177/7 - 48018 Faenza (RA) - Italy
tel. +39.0546.637711 - fax +39.0546.46077
www.mmbsoftware.it - i...@mmbsoftware.it

Le informazioni contenute in questa comunicazione sono riservate e
destinate esclusivamente alla/e persona/e o all'ente sopra indicati. E'
vietato ai soggetti diversi dai destinatari qualsiasi uso, copia,
diffusione di quanto in esso contenuto sia ai sensi dell'art. 616 c.p., sia
ai sensi del DL n. 196/03. Se questa comunicazione Vi e' pervenuta per
errore, Vi preghiamo di rispondere a questa e-mail e successivamente
cancellarla dal Vostro sistema.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAArRkeXu%3DRFSZecehCkR6m1-MadaPBDVxAOoRS3BA_pnrCL_sQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Unwelcome change: Paginating the task queue list

[Jeff Schnitzer]

Hi Google…

Yesterday I noticed that the “task queue” viewer in the cloud console was
changed to paginate the results every 10 entries. I can no longer see the
state of all my queues at a glance. Constantly clicking through four pages
is irksome, especially when there is a vast sea of blank space on my nice
tall monitor.

My app performs a lot of orchestration based on task queues; checking to
see if any of the jobs are backed up is part of our standard measurement of
the general health of the system. This just got a lot more painful.

If you have to paginate, please make the list hundreds long. Not 10. I
heard my entire team scream in agony, one at a time, as they noticed the
change :-(

Thanks,
Jeff

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CADK-0ujKTUv%2BRm6g5y7NzAqkyCYpFdqrmUS-Cj9FGqY5G%3D-sVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Is it possible to pipeline a file upload with a download in Google Cloud Storage?

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Hector,

Glad to hear I've been of help! We'll keep an eye out for the feature 
request and it should be acknowledged quickly.

Best of luck!

Nick
Cloud Platform Community Support

On Thursday, April 28, 2016 at 9:53:54 AM UTC-4, Hector Montaner wrote:
>
> Hi Nick,
>
> yes, I would have to use a Compute Engine instance, mainly because an App 
> Engine Endpoint has a time limit that would be exceeded by large files 
> uploading/downloading. On the other hand, I didn't know that thing you 
> mention about the buffering of the whole response in App Engine, it is good 
> to know, thanks!
>
> Waiting for the upload process to finish before starting the download 
> process is what I was trying to avoid, that's the hole point :)
>
> Thanks for the tip, I will send a Feature Request.
>
> You have been very helpful. Thanks again!
>
> On Tuesday, April 26, 2016 at 6:04:37 PM UTC+2, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Hector,
>>
>> Ah, yes, I was operating with the assumption that the "client" machine 
>> was a server machine itself, although if it's a user's machine and a 
>> browser, the ability to download files in a chunked manner is somewhat 
>> different. The PHP scheme envisioned would work if the PHP machine were a 
>> Compute Engine instance, although be aware that the PHP App Engine runtime, 
>> due to the App Engine serving infrastructure, buffers whole responses until 
>> the request-handler terminates, so a chunked download from a PHP App Engine 
>> module wouldn't function here. 
>>
>> As for network costs, I think it's impossible to avoid network transfer 
>> of data from the upload machine to the machine that the user's browser will 
>> connect to for a chunked download. One stream of data is going to Cloud 
>> Storage, and another is going to a location that it will be possible to 
>> forward the chunks to the user from. 
>>
>> As to the question of filesystem writing, really the only cross-browser 
>> way to do this is with file downloads.
>>
>> At this point, if you don't want to stream to both Cloud Storage and the 
>> machine the client connects to before the upload is completed, it seems 
>> possible that you could just cut losses and wait for the upload to complete 
>> before initiating a download from the client? Is there any particular 
>> reason that's undesirable, other than the time offset? Perhaps the uploads 
>> and downloads will be very large files? Maybe there's a way to structure 
>> the program so that the upload-wait period isn't damaging to the user 
>> experience / system behaviour?
>>
>> If you'd like, you could make a Feature Request in the Public Issue 
>> Tracker  for 
>> the Cloud Platform to have some means of chunked-downloading an object 
>> while it's being chunked-uploaded. We always encourage people to make 
>> Feature Requests, it helps improve the platform!
>>
>> I hope these thoughts have been helpful; let me know your thoughts.
>>
>> Sincerely,
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Tuesday, April 26, 2016 at 9:01:31 AM UTC-4, Hector Montaner wrote:
>>>
>>> Hi Nick,
>>>
>>> Thanks for answering! Your solution has one inconvenient for me: the 
>>> downloading client needs also a bit of sophistication, not only the 
>>> uploading client.
>>>
>>> If I understood correctly, the downloading client will download one 
>>> chunk after another. If this is the case, the browser would have to 
>>> download all chunks, keep them in memory, assemble them into one blob, and 
>>> then trigger the "download" from memory to the user file system. This is a 
>>> problem if the file size is several GBs.
>>>
>>> I know there are some browsers like Chrome that allow writing files to 
>>> internal filesystem so that the assemble process can be done in disk. 
>>> However, I need this process specially for those browsers that do not 
>>> support FileSystem writing :)
>>>
>>> The best solution I can think of is to have an instance machine with for 
>>> example Apache+PHP that accepts an HTTP Get request for the download. The 
>>> PHP would iterate over the chunks and output them to the client in the body 
>>> of the only one HTTP Get request, and wait when the rest of chunks have not 
>>> yet been uploaded. I think this will work, but it would not be cheap, as I 
>>> would have to pay for the instance hours and for the bandwidth consumed to 
>>> send chunks from GAE to the client.
>>>
>>> What is your opinion?
>>>
>>> On Thursday, April 21, 2016 at 11:53:24 PM UTC+2, Nick (Cloud Platform 
>>> Support) wrote:

 Hey Hector,

 While this isn't possible in the way you described exactly, since you 
 can only begin fetching an object once it's been uploaded successfully, 
 there is a solution which accomplishes essentially the same thing, 
 although 
 it will require a slight bit of sophistication in the uploading client to 
 ensure things go well:

 Have the

[google-appengine] Standard Env built-in libs docs missing

[Brian Michelich]

This 
page 
https://cloud.google.com/appengine/docs/python/tools/using-libraries-python-27 
links to the available libraries and versions for the standard environment 
but the page is missing.

https://cloud.google.com/appengine/docs/python/refdocs/libraries/built-in-libraries-27


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/340571e2-25a2-4013-860a-c37d7f581725%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Is it possible to pipeline a file upload with a download in Google Cloud Storage?

[Hector Montaner]

Hi Nick,

yes, I would have to use a Compute Engine instance, mainly because an App 
Engine Endpoint has a time limit that would be exceeded by large files 
uploading/downloading. On the other hand, I didn't know that thing you 
mention about the buffering of the whole response in App Engine, it is good 
to know, thanks!

Waiting for the upload process to finish before starting the download 
process is what I was trying to avoid, that's the hole point :)

Thanks for the tip, I will send a Feature Request.

You have been very helpful. Thanks again!

On Tuesday, April 26, 2016 at 6:04:37 PM UTC+2, Nick (Cloud Platform 
Support) wrote:
>
> Hey Hector,
>
> Ah, yes, I was operating with the assumption that the "client" machine was 
> a server machine itself, although if it's a user's machine and a browser, 
> the ability to download files in a chunked manner is somewhat different. 
> The PHP scheme envisioned would work if the PHP machine were a Compute 
> Engine instance, although be aware that the PHP App Engine runtime, due to 
> the App Engine serving infrastructure, buffers whole responses until the 
> request-handler terminates, so a chunked download from a PHP App Engine 
> module wouldn't function here. 
>
> As for network costs, I think it's impossible to avoid network transfer of 
> data from the upload machine to the machine that the user's browser will 
> connect to for a chunked download. One stream of data is going to Cloud 
> Storage, and another is going to a location that it will be possible to 
> forward the chunks to the user from. 
>
> As to the question of filesystem writing, really the only cross-browser 
> way to do this is with file downloads.
>
> At this point, if you don't want to stream to both Cloud Storage and the 
> machine the client connects to before the upload is completed, it seems 
> possible that you could just cut losses and wait for the upload to complete 
> before initiating a download from the client? Is there any particular 
> reason that's undesirable, other than the time offset? Perhaps the uploads 
> and downloads will be very large files? Maybe there's a way to structure 
> the program so that the upload-wait period isn't damaging to the user 
> experience / system behaviour?
>
> If you'd like, you could make a Feature Request in the Public Issue 
> Tracker  for 
> the Cloud Platform to have some means of chunked-downloading an object 
> while it's being chunked-uploaded. We always encourage people to make 
> Feature Requests, it helps improve the platform!
>
> I hope these thoughts have been helpful; let me know your thoughts.
>
> Sincerely,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, April 26, 2016 at 9:01:31 AM UTC-4, Hector Montaner wrote:
>>
>> Hi Nick,
>>
>> Thanks for answering! Your solution has one inconvenient for me: the 
>> downloading client needs also a bit of sophistication, not only the 
>> uploading client.
>>
>> If I understood correctly, the downloading client will download one chunk 
>> after another. If this is the case, the browser would have to download all 
>> chunks, keep them in memory, assemble them into one blob, and then trigger 
>> the "download" from memory to the user file system. This is a problem if 
>> the file size is several GBs.
>>
>> I know there are some browsers like Chrome that allow writing files to 
>> internal filesystem so that the assemble process can be done in disk. 
>> However, I need this process specially for those browsers that do not 
>> support FileSystem writing :)
>>
>> The best solution I can think of is to have an instance machine with for 
>> example Apache+PHP that accepts an HTTP Get request for the download. The 
>> PHP would iterate over the chunks and output them to the client in the body 
>> of the only one HTTP Get request, and wait when the rest of chunks have not 
>> yet been uploaded. I think this will work, but it would not be cheap, as I 
>> would have to pay for the instance hours and for the bandwidth consumed to 
>> send chunks from GAE to the client.
>>
>> What is your opinion?
>>
>> On Thursday, April 21, 2016 at 11:53:24 PM UTC+2, Nick (Cloud Platform 
>> Support) wrote:
>>>
>>> Hey Hector,
>>>
>>> While this isn't possible in the way you described exactly, since you 
>>> can only begin fetching an object once it's been uploaded successfully, 
>>> there is a solution which accomplishes essentially the same thing, although 
>>> it will require a slight bit of sophistication in the uploading client to 
>>> ensure things go well:
>>>
>>> Have the uploading client send chunks of the file to the Cloud Storage 
>>> API as a multipart upload 
>>> 
>>>  while, 
>>> at the same time, sending these chunks to the other client (or sends them 
>>> to a location where it will be available to the other client upon request).
>>>
>>> The complexity arises w

[google-appengine] Re: Multiple AppEngine 104 errors

[Alexandru Farcaş]

In the last 20 minutes I didn't received 104 errors and the tasks were 
created with success! 
It seems that the application is running as it used to run ..

On Thursday, April 28, 2016 at 1:17:43 PM UTC+3, Ice13ill wrote:
>
> Same for me.
> Also, many 500 and 404 errors and very high latencies.
>
> On Thursday, April 28, 2016 at 1:06:08 PM UTC+3, Alexandru Farcaş wrote:
>>
>> Hi,
>>
>> I have multiple errors with error code 104. I have this behaviour since 
>> 11:50am EEST. 
>> I receive a lot of errors at task creation. I receive this errors but the 
>> tasks are still created in task queue!
>>
>> java.util.ConcurrentModificationException >> too much contention on these 
>>> datastore entities. please try again.
>>
>>
>>  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/499693f3-0ed0-42f7-8660-60074f1d4e9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Multiple AppEngine 104 errors

[Ice13ill]

Same for me.
Also, many 500 and 404 errors and very high latencies.

On Thursday, April 28, 2016 at 1:06:08 PM UTC+3, Alexandru Farcaş wrote:
>
> Hi,
>
> I have multiple errors with error code 104. I have this behaviour since 
> 11:50am EEST. 
> I receive a lot of errors at task creation. I receive this errors but the 
> tasks are still created in task queue!
>
> java.util.ConcurrentModificationException >> too much contention on these 
>> datastore entities. please try again.
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cf9346bb-9d46-4e35-bdf6-4541647f797c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Multiple AppEngine 104 errors

[Alexandru Farcaş]

Hi,

I have multiple errors with error code 104. I have this behaviour since 
11:50am EEST. 
I receive a lot of errors at task creation. I receive this errors but the 
tasks are still created in task queue!

java.util.ConcurrentModificationException >> too much contention on these 
> datastore entities. please try again.


 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/265a7c5f-c593-43cb-87bb-e8748e6b3317%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.