Re: [google-appengine] Re: too many appengine frontend instances
The issue begun with v. 1.9.5 but now the new instaces are created with 1.9.4 so i have about 220 instances on 1.9.5 and 110 on 1.9.4. On 9 May 2014 12:21, "timh" wrote: > I am still on 1.9.4 and not seeing this. > > Is everyone experiencing this rolled over to 1.9.5 ? > > T > > On Friday, May 9, 2014 11:40:19 AM UTC+8, blackdew wrote: >> >> my server make too many Frontend instances >> >> may be it make instance per request >> >> from 2 hours ago >> >> and my last deploy was yesterday may be 24 hours ago >> >> so, help and give me any advice >> >> thanks >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google App Engine" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-appengine/tlQPHCvP-14/unsubscribe > . > To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-appengine. > 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 http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Redirect to original href when using federated login
I used url encode to generate a redirectLink that looks something like this: http%3A%2F%2Fvers.myappid.appspot.com%2page.html%3Flocale%3Dro%23m%3myhistorytoken Now, when I call the createLoginURL method i get this: http://vers.myappid.appspot.com/_ah/login_redir?claimid=www.google.com/accounts/o8/id&continue=http://vers.myappid.appspot.com/ So now, even the link parameters (charactes after '?') are missing from the continue link. Whan am I doing woring ? Maybe i need to specify some other parameters? (I used URLEncoder.encode(originalHref, "ISO-8859-1") in java to generate the redirectLink for the google openID provider) and userService.createLoginURL(redirectLink, null, e.getValue(), new HashSet()) to get the login URL. On 14 February 2012 08:45, Robert Kluin wrote: > Maybe I'm not getting what you're saying here, but perhaps you should > urlencode the continue url. > > > > > > > On Mon, Feb 13, 2012 at 11:41, Ice13ill wrote: > > I'm using federated login for my app authentication and I have the > > following issue: when users connect with google OpenID the auth > > service doesn't redirect to my original href (redirects to my domain > > + > > the url params but ignores all information after "#"). > > To create the login link I use "www.google.com/accounts/o8/id" > > > > When I test in development mode the redirection process works fine. > > > > Also, until 12-16 months ago, I used the Google accounts API option in > > my app setting and I > > remember that after login, the redirect link back to my app contained > > the characters after the history token ( "#" ). > > Is there a workaround for this? or is something I may be doing wrong? > > > > -- > > 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 group, send email to > google-appengine+unsubscr...@googlegroups.com. > > 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Sending email without warning "This message may not have been sent by..."
So if the user that sends email belongs to that group list, the warning will not appear? On Dec 21, 2011 6:51 PM, "voscausa" wrote: > I'am not very familiar with groups. But I know that in some groups > everybody can address the group members. Than it is not clear for the > group, who has send the message. In that case, it is not a GAE problem, but > a group authorization problem. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/Np5U4W3R0lEJ. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Idle instances do not turn off automatically. Please help
I also noticed that on my default version there are two instances with 1h53m age and one is with 1 request, the other with 2. Another instance with 1h33m age has 4 requests... so the instances will not shutdown after 15 min of inactivity. On 23 November 2011 13:30, Ice13ill wrote: > I deployed yesterday a version of my app for testing purposes. I > checked the number of instances on that version today and I noticed > that there were 5 instances active, each one with 24h of age (aprox.). > But I didn't do any tests in the last 15-16 hours. > I also checked if there the number of requests changed in the last > 15-20 minutes and it didn't > > I also noticed that on my default version, i have about 5 instances > with 1h20m each... lets say a total of about 6.5 h for the last 1.5 > hours (real time). But my dashboard shows a total of 4.6 hours. (the > counter was reset 3.5 hours ago, relative to the time when i'm writing > this post). > Until today, everything was fine. I set the number of idle instances > to 1 (max idle instances, about a week and a half ago) and on my > default version were 2, or 3 maximum instances active. It's like the > instance scheduler is not working correctly. > -- 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 group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Idle instances and pending latency management advice
Well, most of my CPU usage is due to tasks background work (about 80%) and also, a large number of datastore writes influences a rise in costs. On 7 November 2011 17:29, Adrian Scott wrote: > I dropped ours from 3 to 2 minimum idle instances, and saw significant > drop in daily cost. > > 7-9 user requests per minute shouldn't be too much of a hit (depending on > how much time is used to serve them and the background tasks they spawn of > course)... > > -- > Adrian Scott, Ph.D. > CEO, Founder > CoderBuddy > http://www.coderbuddy.com/ <-- Create a Google App Engine app in a minute > without installing anything > > > > On Mon, Nov 7, 2011 at 10:22 AM, Ice13ill wrote: > >> Hello, my app has about 7-9 user requests per minute and my settings >> for idle instances and pending latencies are set to Automatic. >> These requests also trigger tasks creation (for some background >> computing and datastore writes). >> I need some basic advice for managing my settings on idle instances >> and pending latencies (at least...) so that my costs are kept as low >> as possible, according to the new pricing model (articles, other group >> threads, or documentation links would be very appreciated) >> >> -- >> 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 group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Maximum concurrent user requests
Well, the requests are independent form each other (threadsafe) and are only related to datastore (each request also triggers task creation for different log writes). Should't all request that arrive "at the same time" be resolved in parallel ? On 16 October 2011 20:34, Brandon Wirtz wrote: > > Concurrency isn't as "concurrent" as a lot of people think it is. Just like > Multi-Tasking. > > If your App does "Calculate the pi to the power of X and return the > Significant Digit in Y position" Your App will consume 100% of the CPU and > you get 0 Concurrent request. If it does so fast enough the Pending > Latency > may allow a single instance to respond to a bunch of requests that arrive > at > the same time, but they will process in Serial. > > If your app does "Fetch X URL and return bytes 1234 through 4321" Most of > the time will be spent in the FetchURL Api, and while that is happening > other requests can execute. > > Because of this My APP that uses about 98% CPU from API's has HUGE > concurrency on Python 2.7. but Huge is still something like 8 not 80. But > when you pay for instances, not consumed CPU this saved me a lot of money. > > In any event, your answer is: It depends on how you are using the CPU > Cycles, and how you use API's or other things that would create a wait > state, along with what the pending latency is. > > > -Original Message- > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Ice13ill > Sent: Sunday, October 16, 2011 9:25 AM > To: Google App Engine > Subject: [google-appengine] Maximum concurrent user requests > > Hello, i know that you can allow concurrent user requests, for example, in > java, by specifying threadsafe = true in your appengine- web.xml, but how > many requests can be actually executed by a servlet in parallel ? > For example, if N users make a request at the same moment, will there be a > number of requests put into wait ?. Let's say M user requests will be > treated (M < N ) and M-N requests will wait ? > > -- > 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 group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: App Engine SDK 1.5.4 released!
I forgot to reply, but now it works... i didn't change anything On Sep 18, 2011 11:21 PM, "Robert Kluin" wrote: > You sure the index is identical? > > > > On Tue, Sep 13, 2011 at 05:25, Ice13ill wrote: >> I've been expecting the new datastore query improvement... >> I have a question related to that feature: i have deployed a new >> version with Java SDK 1.5.4 to test queries that previously failed, >> but it seams they still fail immediately, also requesting an index >> that is already built. Also, these queries work in Datastore Viewer. >> Is it something i'm missing ? Do I have to delete the index and re- >> built it ? >> >> >> On Sep 13, 3:43 am, pdknsk wrote: >>> When will the docs for async memcache be added? I've got one >>> particular question. >>> >>> In transactions, when you use db.put_async(), the transaction >>> guarantees the put even if get_result() is not called. As I understand >>> it, the transaction automatically calls get_result() for the put. >>> >>> How is this handled for async memcache? Unlike db put/get, memcache >>> set/get does not raise an exception, but returns True/False. >> >> -- >> 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 group, send email to google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] URL fetch timeout bigger than 10 sec
Thank you for your response. That is the same solution i found, for both cases. I thought that backends could have helped me. On Sep 15, 2011 5:39 PM, "Rishi Arora" wrote: -- 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 group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Suddenly started to get "Unauthorized sender" when sending emails
I had a user that contained dot in its name and worked. It also contained dash... the sender that had only a dot still triggers the error On Aug 13, 2011 1:58 PM, "bFlood" wrote: > > +1 sender has a period in it > > On Aug 13, 3:09 am, Jan Muller wrote: >> My sender address also contains . >> >> Jan Müller >> >> On Sat, Aug 13, 2011 at 2:12 AM, Joshua Smith wrote: >> >> >> >> >> >> >> >> > +1. My problem sender does, indeed, have a . in the account name. >> >> > On Aug 12, 2011, at 7:17 PM, Takashi Matsuo (Google) wrote: >> >> > Hi everyone. >> >> > We're aware of this issue and working for the fix. >> >> > The issue we're seeing is that if the sender's(who is also an app's owner) >> > mail address contains "." (dot), the mail sending call raises an error. >> >> > Sorry for the inconvenience. >> > If you observe different issue, please let us know. >> >> > -- Takashi >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Google App Engine" group. >> > To view this discussion on the web visit >> >https://groups.google.com/d/msg/google-appengine/-/o5SeyhH4eSkJ. >> > To post to this group, send email to google-appengine@googlegroups.com. >> > To unsubscribe from this group, send email to >> > google-appengine+unsubscr...@googlegroups.com. >> > 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 google-appengine@googlegroups.com. >> > To unsubscribe from this group, send email to >> > google-appengine+unsubscr...@googlegroups.com. >> > 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Suddenly started to get "Unauthorized sender" when sending emails
This sounds bad... So you guys also have a sender that worked, now it
doesn't work, but other senders do work ? (that were also added to
Permissions list)
2011/8/13 Jan Muller
> Yes, i tried it. No results :(
> Dne 13.8.2011 0:02 "Andrei Cosmin Fifiiţă"
> napsal(a):
>
> > Has anyone tried to remove the user and then send an invitation to add it
> > again ?
> >
> > On 13 August 2011 00:57, Ice13ill wrote:
> >
> >> I tried to change the sending user and it worked. When i changed it
> >> back the the original one i still received the
> >> javax.mail.SendFailedException: Send failure error. It worked fine
> >> until today (the user was added to Permissions as Developer; I tried
> >> to change it to Owner and still no success).
> >> What could the problem be?
> >>
> >> On Aug 12, 8:01 pm, iMM Braga wrote:
> >> > This still repros for me.
> >> >
> >> > On 12 Ago, 16:58, Robert Kluin wrote:
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > > When you guys see stuff like this, I'd suggest filing a production
> >> > > issue and including a link to the issue here. I think that will help
> >> > > Googlers track the problem and get a better feel for the scale of
> the
> >> > > issue.
> >> > >
> >> http://code.google.com/p/googleappengine/issues/entry?template=Produc.
> ..
> >> >
> >> > > Robert
> >> >
> >> > > On Fri, Aug 12, 2011 at 11:35, Joshua Smith <
> joshuaesm...@charter.net>
> >> wrote:
> >> > > > The last one of these errors in my logs is 13:33 ago, so I guess
> they
> >> fixed it?
> >> >
> >> > > > GAE Team: Some comment on downtime-notify would be appropriate
> here.
> >> >
> >> > > > On Aug 12, 2011, at 11:14 AM, iMM Braga wrote:
> >> >
> >> > > >> I am having exactly the same problem using the email address of
> my
> >> App
> >> > > >> Owner!
> >> > > >> This email address has always worked.
> >> >
> >> > > >> is the email API broken?
> >> >
> >> > > >> We need Google support on this.
> >> >
> >> > > >> On 12 Ago, 14:44, bFlood wrote:
> >> > > >>> I'm getting these too and the sender is definitely an admin on
> the
> >> > > >>> account (in fact it's the one used to deploy, so I know it's
> valid
> >> and
> >> > > >>> working)
> >> >
> >> > > >>> help Google, no emails are going out
> >> >
> >> > > >>> On Aug 12, 1:08 am, anatoliy
> wrote:
> >> >
> >> > > >>>> Hi!
> >> >
> >> > > >>>> Tonight appengine started to throw:
> >> >
> >> > > >>>> javax.mail.SendFailedException: Send failure
> >> > > >>>> (javax.mail.MessagingException: Illegal Arguments
> >> > > >>>> (java.lang.IllegalArgumentException: Unauthorized Sender:
> >> Unauthorized
> >> > > >>>> sender))
> >> >
> >> > > >>>> for the same code as was working perfectly yesterday.
> >> >
> >> > > >>>> Sender is set using this code:
> >> > > >>>> mimeMsg.setFrom(new InternetAddress("my app ad...@gmail.com",
> "my
> >> app
> >> > > >>>> admin"));
> >> >
> >> > > >>>> Anyone else having same problem?
> >> >
> >> > > >>>> anatoliy- Ocultar texto citado -
> >> >
> >> > > >>> - Mostrar texto citado -
> >> >
> >> > > >> --
> >> > > >> 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 group, send email to
> >> google-appengine+unsubscr...@googlegroups.com.
> >> > > >> For more options, visit this group athttp://
> >> groups.google.com/group/google-appengine?hl=en.
> &g
Re: [google-appengine] Re: Suddenly started to get "Unauthorized sender" when sending emails
Has anyone tried to remove the user and then send an invitation to add it
again ?
On 13 August 2011 00:57, Ice13ill wrote:
> I tried to change the sending user and it worked. When i changed it
> back the the original one i still received the
> javax.mail.SendFailedException: Send failure error. It worked fine
> until today (the user was added to Permissions as Developer; I tried
> to change it to Owner and still no success).
> What could the problem be?
>
> On Aug 12, 8:01 pm, iMM Braga wrote:
> > This still repros for me.
> >
> > On 12 Ago, 16:58, Robert Kluin wrote:
> >
> >
> >
> >
> >
> >
> >
> > > When you guys see stuff like this, I'd suggest filing a production
> > > issue and including a link to the issue here. I think that will help
> > > Googlers track the problem and get a better feel for the scale of the
> > > issue.
> > >
> http://code.google.com/p/googleappengine/issues/entry?template=Produc...
> >
> > > Robert
> >
> > > On Fri, Aug 12, 2011 at 11:35, Joshua Smith
> wrote:
> > > > The last one of these errors in my logs is 13:33 ago, so I guess they
> fixed it?
> >
> > > > GAE Team: Some comment on downtime-notify would be appropriate here.
> >
> > > > On Aug 12, 2011, at 11:14 AM, iMM Braga wrote:
> >
> > > >> I am having exactly the same problem using the email address of my
> App
> > > >> Owner!
> > > >> This email address has always worked.
> >
> > > >> is the email API broken?
> >
> > > >> We need Google support on this.
> >
> > > >> On 12 Ago, 14:44, bFlood wrote:
> > > >>> I'm getting these too and the sender is definitely an admin on the
> > > >>> account (in fact it's the one used to deploy, so I know it's valid
> and
> > > >>> working)
> >
> > > >>> help Google, no emails are going out
> >
> > > >>> On Aug 12, 1:08 am, anatoliy wrote:
> >
> > > Hi!
> >
> > > Tonight appengine started to throw:
> >
> > > javax.mail.SendFailedException: Send failure
> > > (javax.mail.MessagingException: Illegal Arguments
> > > (java.lang.IllegalArgumentException: Unauthorized Sender:
> Unauthorized
> > > sender))
> >
> > > for the same code as was working perfectly yesterday.
> >
> > > Sender is set using this code:
> > > mimeMsg.setFrom(new InternetAddress("my app ad...@gmail.com", "my
> app
> > > admin"));
> >
> > > Anyone else having same problem?
> >
> > > anatoliy- Ocultar texto citado -
> >
> > > >>> - Mostrar texto citado -
> >
> > > >> --
> > > >> 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 group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> > > >> For more options, visit this group athttp://
> 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
> google-appengine@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> > > > For more options, visit this group athttp://
> groups.google.com/group/google-appengine?hl=en.-Ocultar texto citado -
> >
> > > - Mostrar texto citado -
>
> --
> 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 group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Task Creation failing at a high rate since 1.5 pre release
I encountered another problem. I seamed that when a task was added to my task queue, it was added three or four times. (i believe this happened a few times). For example: at a certain action, a task is created: this task generates a document (based on some processing) delivers an email an then records some data. If the task is created 3 times (although it was added once), it's not good. Is there a way to detect this problem ? On 5 May 2011 04:13, nischalshetty wrote: > Yeah, retrying works. But, this was never needed till the new release of 1.5 > was announced. My suspicion is on that (btw, some major changes to task > queues on the way with the 1.5 release, exciting times ahead). > Anyways, as @Greg has mentioned here, it's a relief to know that someone > from Google is looking into this. Hoping things get sorted out soon. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group.I > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Task Creation failing at a high rate since 1.5 pre release
I think it will work... Retry about 5 times (eventually a few seconds between retries) will probably help. On 4 May 2011 21:26, PK wrote: > Same problem this morning. Here is the traceback I see: > > Task failed to be added to queue > Traceback (most recent call last): > File "/base/data/home/apps/X/1-5-6.350136996983844962/swplatform/ > util/ctl/generic_handler.py", line 637, in do_domain > queue.add(tsk, transactional = self.transactional()) > File "/base/python_runtime/python_lib/versions/1/google/appengine/ > api/taskqueue/taskqueue.py", line 1120, in add > self.__AddTasks(tasks, transactional, > self.__FillAddPushTasksRequest) > File "/base/python_runtime/python_lib/versions/1/google/appengine/ > api/taskqueue/taskqueue.py", line 1163, in __AddTasks > raise self.__TranslateError(e.application_error, e.error_detail) > TransientError > > Is it worth changing the code to retry such issues? I ll attempt it > anyway. > > PK > http://www.gae123.com > > -- > 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 group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Task Creation failing at a high rate since 1.5 pre release
I still get these errors... I can't say its a high percentage, but it's a significant rate. On 4 May 2011 19:47, Robert Kluin wrote: > I've seen a few bursts of transient errors on a couple Python apps as > well. They seemed to have cleared up for me though. > > What percentage of task adds are giving errors? > > > > Robert > > > > > > On Wed, May 4, 2011 at 12:31, Ice13ill wrote: >> I get this exception too... It seams that there is a problem when >> adding tasks to a queue ? >> >> On May 4, 5:55 pm, nischalshetty wrote: >>> Hi, >>> >>> I'm seeing a lot of task failures after the announcement of the pre release >>> 1.5 sdk. I haven't changed my sdk (I'm on 1.4.2 java sdk for gae). Tasks >>> are very critical to my application. My app creates a lot of tasks every >>> minute. Can you please look into this? >>> >>> Here's the stack trace : >>> >>> com.google.appengine.api.taskqueue.TransientFailureException: Unknown >>> at >>> com.google.appengine.api.taskqueue.QueueApiHelper.translateError(QueueApiHe >>> lper.java:58) >>> at >>> com.google.appengine.api.taskqueue.QueueApiHelper.translateError(QueueApiHe >>> lper.java:112) >>> at >>> com.google.appengine.api.taskqueue.QueueApiHelper.makeSyncCall(QueueApiHelp >>> er.java:32) >>> at >>> com.google.appengine.api.taskqueue.QueueImpl.add(QueueImpl.java:466) >>> at >>> com.google.appengine.api.taskqueue.QueueImpl.add(QueueImpl.java:412) >>> at >>> com.google.appengine.api.taskqueue.QueueImpl.add(QueueImpl.java:397) >>> >>> at sun.reflect.GeneratedMethodAccessor62.invoke(Unknown Source) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp >>> l.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:616) >>> at >>> com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M >>> ethod_$1.run(Method_.java:165) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at >>> com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M >>> ethod_.privilegedInvoke(Method_.java:163) >>> at >>> com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M >>> ethod_.invoke_(Method_.java:124) >>> at >>> com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.M >>> ethod_.invoke(Method_.java:43) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionI >>> nvocation.java:404) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultAct >>> ionInvocation.java:267) >>> >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invocation.java:224) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invocation.java:223) >>> at >>> com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStac >>> k.java:455) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocat >>> ion.java:221) >>> at >>> com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept( >>> DefaultWorkflowInterceptor.java:221) >>> at >>> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(Metho >>> dFilterInterceptor.java:86) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invocation.java:224) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invocation.java:223) >>> at >>> com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStac >>> k.java:455) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocat >>> ion.java:221) >>> at >>> com.opensymphony.xwork2.validator.ValidationInterceptor.doIntercept(Validat >>> ionInterceptor.java:150) >>> at >>> org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor.d >>> oIntercept(AnnotationValidationInterceptor.java:48) >>> at >>> com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(Metho >>> dFilterInterceptor.java:86) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invocation.java:224) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invocation.java:223) >>> at >>> com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStac >>> k.java:455) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocat >>> ion.java:221) >>> at >>> com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(Co >>> nversionErrorInterceptor.java:123) >>> at >>> com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultAction >>> Invoc
Re: [google-appengine] Re: Problem with built in indices and lists of properties
The zig-zag doesnt try and then gives up... it just doesnt try anything... it knows exactly when the query is executed... The fail happens very quickly... 100ms aprox... Second.. i tryied with 200 limit (which is max) and works On 15 April 2011 22:04, Stephen Johnson wrote: > Hi Andrei, > Well, the datastore viewer defaults to a limit of 20 (unless you change it > via url). Did you have any limit set on your low-level api call?? I don't > know when the zig zag merge join decides it has enough and gives up. Either > it is based on some time threshold or it is based on number of candidate > keys it has thrown away or perhaps some other metric. So it's definitely > possible that the datastore viewer could show 20 records while your code has > some higher limit (or none) and thus it surpasses the threshold and aborts. > Stephen > > 2011/4/15 Andrei Cosmin Fifiiţă >> >> Well the Stephen's explanation seems more logical... >> So that means that the limit count influences the success of the query ? >> I had a situation where my query (with 3 params) failed in my app >> (using low-level api) but succeeded in the App console (datastore >> viewer), using GQL... How can that be ? >> >> On 14 April 2011 21:59, Alexandru Farcaş >> wrote: >> > In this presentation, >> > http://dl.google.com/io/2009/pres/W_0415_Building_Scalable_Complex_App_Engines.pdf, >> > at slide 53, google say that "to many overlapping values = lots of zig >> > - zagging" >> > >> > >> > I test my app with queries with individual results (9, <500) and I >> > didn't receive "Datastore need index exception...". >> > When I get this exception the query time is ~80ms. It looks like it >> > didn't try to zig zag anything... >> > >> > >> > On Apr 14, 8:34 pm, Robert Kluin wrote: >> >> Hi Stephen, >> >> Yeah, I didn't explain very that clearly at all; I think you did a >> >> significantly better job: "you have too few overlapping entities in >> >> the two sets." That is exactly what I was trying to say. ;) >> >> >> >> For those interested, the merge-join algorithm is explained here: >> >> >> >> http://sites.google.com/site/io/under-the-covers-of-the-google-app-en... >> >> >> >> Robert >> >> >> >> 2011/4/15 Stephen Johnson : >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > Hi Alexander, >> >> > I'm sorry to disagree with Robert, but the zig zag merge-join doesn't >> >> > return >> >> > the various rows for each index back to the application code to >> >> > combine them >> >> > in the application. It's a difficult algorithm to explain in an email >> >> > but >> >> > basically the problem looks to be that with the 9 entities and < >> >> > 500 >> >> > entites case you have too few overlapping entites in the two sets. >> >> > Basically, think of it as you start off with 9 possible >> >> > candidates that >> >> > could be part of the result set. Now, the zig zag merge join goes and >> >> > checks >> >> > the other list (the less than 500 list), but it basically does this >> >> > one at a >> >> > time. Every time it doesn't find a match it throws that candidate >> >> > away and >> >> > goes on to the next. It has to do this for each equality filter so if >> >> > you >> >> > have 4 then it has to check for indexes for each candidate. You can >> >> > see that >> >> > this can take some time. Now if it finds enough matches fast enough >> >> > to >> >> > satisfy the query limit that is requested to be returned then all is >> >> > fine, >> >> > but if it has to keep throwing candidates away and trying new ones >> >> > than it >> >> > times out and reports that it needs an index. So with your queries >> >> > that have >> >> > large individual results (9, 5 and 5) you obviously have >> >> > a large >> >> > overlapping set and it finds enough matches very quickly, but when >> >> > you have >> >> > large sets combined with small sets (9 and <500) then you have >> >> > few >> >&g
Re: [google-appengine] Re: Problem with built in indices and lists of properties
Well the Stephen's explanation seems more logical... So that means that the limit count influences the success of the query ? I had a situation where my query (with 3 params) failed in my app (using low-level api) but succeeded in the App console (datastore viewer), using GQL... How can that be ? On 14 April 2011 21:59, Alexandru Farcaş wrote: > In this presentation, > http://dl.google.com/io/2009/pres/W_0415_Building_Scalable_Complex_App_Engines.pdf, > at slide 53, google say that "to many overlapping values = lots of zig > - zagging" > > > I test my app with queries with individual results (9, <500) and I > didn't receive "Datastore need index exception...". > When I get this exception the query time is ~80ms. It looks like it > didn't try to zig zag anything... > > > On Apr 14, 8:34 pm, Robert Kluin wrote: >> Hi Stephen, >> Yeah, I didn't explain very that clearly at all; I think you did a >> significantly better job: "you have too few overlapping entities in >> the two sets." That is exactly what I was trying to say. ;) >> >> For those interested, the merge-join algorithm is explained here: >> http://sites.google.com/site/io/under-the-covers-of-the-google-app-en... >> >> Robert >> >> 2011/4/15 Stephen Johnson : >> >> >> >> >> >> >> >> > Hi Alexander, >> > I'm sorry to disagree with Robert, but the zig zag merge-join doesn't >> > return >> > the various rows for each index back to the application code to combine >> > them >> > in the application. It's a difficult algorithm to explain in an email but >> > basically the problem looks to be that with the 9 entities and < 500 >> > entites case you have too few overlapping entites in the two sets. >> > Basically, think of it as you start off with 9 possible candidates that >> > could be part of the result set. Now, the zig zag merge join goes and >> > checks >> > the other list (the less than 500 list), but it basically does this one at >> > a >> > time. Every time it doesn't find a match it throws that candidate away and >> > goes on to the next. It has to do this for each equality filter so if you >> > have 4 then it has to check for indexes for each candidate. You can see >> > that >> > this can take some time. Now if it finds enough matches fast enough to >> > satisfy the query limit that is requested to be returned then all is fine, >> > but if it has to keep throwing candidates away and trying new ones than it >> > times out and reports that it needs an index. So with your queries that >> > have >> > large individual results (9, 5 and 5) you obviously have a >> > large >> > overlapping set and it finds enough matches very quickly, but when you >> > have >> > large sets combined with small sets (9 and <500) then you have few >> > overlaps but lots of checking to do. >> > I hope this helps and if I misinterpreted Robert's post then I apologize to >> > him. >> > Stephen >> >> > On Thu, Apr 14, 2011 at 8:36 AM, Alexandru Farcaş >> > wrote: >> >> >> Hi Robert, >> >> Thanks for your answer. >> >> If the number of results returned by each filter individually is >> >> smaller than, let's say 1000, the "final" number of results will be >> >> returned correctly? >> >> I want to know if there are some known limits for this type of query >> >> on a single list property (maybe for the size of the list, for the >> >> number of the results returned by each filter, for the number of >> >> filters, etc...). I didn't find the answer for this question. >> >> In all queries that returns datastore need index exception I have one >> >> filter that returns almost 9 entities and one that returns < 500 >> >> results. >> >> But I have also many queries with 3 filters (9 results, 5 >> >> results, 5 results) that returns the correct results. >> >> >> Hi Andrei, >> >> Yes, almost the same queries: the difference is that in the second >> >> table I have a single list property. This list contains the rest of >> >> fields from the first table. >> >> I tried to limit the number of the results from datastore viewer but >> >> with the same result :(. >> >> >> On Apr 14, 5:03 pm, Andrei Cosmin Fifiiţă
Re: [google-appengine] Re: Problem with built in indices and lists of properties
And also, i limit the number of results (for ex when implementing pagination)... Does that affect the success of the query ? 2011/4/14 Andrei Cosmin Fifiiţă : > I don't want to create custom indices cause they will fail... but does the > order of the equality filters matter? > > On Apr 14, 2011 3:38 AM, "Robert Kluin" wrote: > -- 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 group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Problem with built in indices and lists of properties
I don't want to create custom indices cause they will fail... but does the order of the equality filters matter? On Apr 14, 2011 3:38 AM, "Robert Kluin" wrote: -- 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 group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: SDK 1.4.3 has been released!
Are you using Master/Slave or HR? 2011/4/7 Sérgio Lopes : > Hi Ikai! > I didn't notice any performance issue here. > However I'm experiencing a lot of errors lately during instance startup. > I've AlwaysOn and the "Instances" panel clearly shows that 2 instances are > always ok, with a large Age. But one of those instances is constantly being > shut down and restarting a lot. There are also many startup requests with > "error 500". The error messages usually are: > > The process handling this request unexpectedly died. This is likely to cause > a new process to be used for the next request to your application. (Error > code 203) > > or > > java.lang.NullPointerException > at java.lang.Class.isAssignableFrom(Native Method) > at > org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:256) > > . > > A serious problem was encountered with the process that handled this > request, causing it to exit. This is likely to cause a new process to be > used for the next request to your application. If you see this message > frequently, you may be throwing exceptions during the initialization of your > application. (Error code 104) > > or > > Uncaught exception from servlet > javax.servlet.UnavailableException: Initialization failed. > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:200) > at > com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:168) > > > > -- > 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 group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Huge latencies and so many 500 errors/Deadline Exceeded
I understand that the costs are about 3 times higher. Is that correct ? 2011/4/4 JH : > I use HR and have not had 1 datastore timeout since switching. I > highly recommend it. > > On Apr 4, 7:34 am, Andrei Cosmin Fifiiţă > wrote: >> Hmmm... nobody... >> On Apr 2, 2011 3:36 PM, "Andrei Cosmin Fifiiţă" >> wrote: >> >> >> >> >> >> >> >> > Anyone with HR? >> > On Apr 1, 2011 8:31 PM, "Everson Alves da Silva" >> wrote: >> >> I'm using Master/Slave Replication >> >> >> -- >> >> 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 group, send email to >> > google-appengine+unsubscr...@googlegroups.com. >> >> 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Huge latencies and so many 500 errors/Deadline Exceeded
Hmmm... nobody... On Apr 2, 2011 3:36 PM, "Andrei Cosmin Fifiiţă" wrote: > Anyone with HR? > On Apr 1, 2011 8:31 PM, "Everson Alves da Silva" wrote: >> I'm using Master/Slave Replication >> >> -- >> 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 group, send email to > google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Huge latencies and so many 500 errors/Deadline Exceeded
Anyone with HR? On Apr 1, 2011 8:31 PM, "Everson Alves da Silva" wrote: > I'm using Master/Slave Replication > > -- > 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 group, send email to google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: SDK 1.4.3 has been released!
What do Prospective and Retrospective searches refer to ? On 31 March 2011 20:31, tempy wrote: > Hi, > Just want to verify... the Prospective Search API is NOT the same > thing as the "full text search" API thats mentioned in the roadmap, is > that right? > > I certainly hope so, as I very much need Retrospective and not > Prospective search. > > -- > 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 group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: SDK 1.4.3 has been released!
Well, i my servlet methods (i use GWT RPC) do not use Thread specific
operations and they don't access any shared objects other than
Memcache objects, Session, or Datastore entities.
On 31 March 2011 18:20, Remigius wrote:
> Ice13ill,
>
> There's a short and a long long answer to your question.
>
> The short one: If you don't already know what "proper thread
> synchronization" is, leave the option switched off.
>
> The long one: Switching it on allows multiple HTTP requests to be
> handled concurrently by the same instance of your Java servlet. This
> means that all data structures that are accessible through instance
> members or static members can be accessed simultaneously by more than
> one running thread, which may result in unexpected errors if a thread
> manipulates a structure in a way that leaves it temporarily in an
> inconsistent state. Such errors are hard to trace as they may occur
> infrequently and be impossible to reproduce in a deterministic way.
> There are ways to ensure that such manipulations can not be
> interrupted, which is known as synchronization. There is a lot of
> information around (on the net and in printed form) on threadsafe
> programming in general and synchronization in particular.
>
> Cheers, Remigius.
>
> On 31 Mrz., 13:51, Ice13ill wrote:
>> What dies thread safe really mean ? ("your application code needs to
>> use proper thread synchronization before you enable ").
>> Can someone give some hints?
>>
>> On Mar 31, 10:53 am, Simon Knott wrote:
>>
>>
>>
>>
>>
>>
>>
>> > Ah ignore my message, I've just tested it - in SDK 1.4.2 it throws an error
>> > and in SDK 1.4.3 it doesn't. Cheers for the info, I should really have
>> > guessed at that...
>
> --
> 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 group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> 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 google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Huge latencies and so many 500 errors/Deadline Exceeded
And also, what happeneds to if i move an entitty from one application to another ? the entity key remains the same ? If not, links between my entities will be broken right ? 2011/3/31 Andrei Cosmin Fifiiţă : > So the option of moving my data to an application that uses HR will > only appear if i disable all writes to datastore ? > > On 31 March 2011 17:09, Gopal Patel wrote: >> HR is REPAIRED version of MS I think. >> >> AFAIK , they have built the moving facility in to the admin console. >> you have to make your ds read only for a while and move the data , >> upload your app and again stop read only mode. >> >> On Thu, Mar 31, 2011 at 5:10 PM, Ice13ill wrote: >>> 1. My datastore has about 75 entities and i understand that i have >>> to move all my entities to another app. So what advice can you give me >>> in moving my data? >>> 2. Are there any known issues with HR ? I mean, is it really so >>> great ? (latencies, errors, etc). I seams to me that the Master/Slave >>> datastores will not be "repaired" (i read that somewhere i think... ) >>> >>> On Mar 31, 12:26 am, "Brandon Wirtz" wrote: >>>> This has not been an issue on HR. You might consider a move. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -Original Message- >>>> From: google-appengine@googlegroups.com >>>> >>>> [mailto:google-appengine@googlegroups.com] On Behalf Of Ice13ill >>>> Sent: Wednesday, March 30, 2011 2:11 PM >>>> To: Google App Engine >>>> Subject: [google-appengine] Huge latencies and so many 500 errors/Deadline >>>> Exceeded >>>> >>>> In the last few days the rise in 500 errors (Deadline Exceeded most of >>>> them) made the interaction with my application almost impossible. >>>> It seams that the requests from client side don't even reach our >>>> implemented servlet methods (GWT RPC). >>>> >>>> Until a few days ago, some 500/203 errors spawned once in a while ( many >>>> developers reported that) but now i can barley use the application. >>>> >>>> Please resolve this issue as soon as possible ! >>>> >>>> -- >>>> 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 group, send email to >>>> google-appengine+unsubscr...@googlegroups.com. >>>> For more options, visit this group >>>> athttp://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 google-appengine@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine+unsubscr...@googlegroups.com. >>> 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 google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: Huge latencies and so many 500 errors/Deadline Exceeded
So the option of moving my data to an application that uses HR will only appear if i disable all writes to datastore ? On 31 March 2011 17:09, Gopal Patel wrote: > HR is REPAIRED version of MS I think. > > AFAIK , they have built the moving facility in to the admin console. > you have to make your ds read only for a while and move the data , > upload your app and again stop read only mode. > > On Thu, Mar 31, 2011 at 5:10 PM, Ice13ill wrote: >> 1. My datastore has about 75 entities and i understand that i have >> to move all my entities to another app. So what advice can you give me >> in moving my data? >> 2. Are there any known issues with HR ? I mean, is it really so >> great ? (latencies, errors, etc). I seams to me that the Master/Slave >> datastores will not be "repaired" (i read that somewhere i think... ) >> >> On Mar 31, 12:26 am, "Brandon Wirtz" wrote: >>> This has not been an issue on HR. You might consider a move. >>> >>> >>> >>> >>> >>> >>> >>> -Original Message- >>> From: google-appengine@googlegroups.com >>> >>> [mailto:google-appengine@googlegroups.com] On Behalf Of Ice13ill >>> Sent: Wednesday, March 30, 2011 2:11 PM >>> To: Google App Engine >>> Subject: [google-appengine] Huge latencies and so many 500 errors/Deadline >>> Exceeded >>> >>> In the last few days the rise in 500 errors (Deadline Exceeded most of >>> them) made the interaction with my application almost impossible. >>> It seams that the requests from client side don't even reach our >>> implemented servlet methods (GWT RPC). >>> >>> Until a few days ago, some 500/203 errors spawned once in a while ( many >>> developers reported that) but now i can barley use the application. >>> >>> Please resolve this issue as soon as possible ! >>> >>> -- >>> 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 group, send email to >>> google-appengine+unsubscr...@googlegroups.com. >>> For more options, visit this group >>> athttp://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 google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> 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 google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: High rate for errors of type 500 ?
Right... now it seams there's like a 500 error party... Latencies are high and queries have a high error rate. 2010/11/6 Andrei Cosmin Fifiiţă > Wow... now it seams that the latencies are very very low... I've haven't > experienced such good response times for my app's queries. I hope they'll > keep this up ! :) > > > On Sat, Nov 6, 2010 at 6:24 PM, Jeremy Benetz wrote: > >> Yes. I'm getting a lot of 500 errors. It has nothing to do with my code >> since I'm just trying to access the admin dashboard. That's what's giving >> me the 500 errors. >> >> -- >> 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-appeng...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com >> . >> 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] Re: High rate for errors of type 500 ?
Wow... now it seams that the latencies are very very low... I've haven't experienced such good response times for my app's queries. I hope they'll keep this up ! :) On Sat, Nov 6, 2010 at 6:24 PM, Jeremy Benetz wrote: > Yes. I'm getting a lot of 500 errors. It has nothing to do with my code > since I'm just trying to access the admin dashboard. That's what's giving > me the 500 errors. > > -- > 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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com > . > 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
