Greg, Can you formulate a reason why the minimum of 3 instances should be left on given The Scheduler's new role?
I had though "min 3" an artifact of the old $9/mn plan, and that anyone with a low-volume site looking for minimum pricing would set max idle to 1, and then vary latency slider according to how much he/ she wants users to be affected by new spinups should a burst of traffic hit the site. Thanks, stevep On Sep 6, 8:45 pm, "Gregory D'alesandre" <[email protected]> wrote: > I think we've tracked the bug down. We are currently treating Always-On as > if it is 3 min idle instances. When you try to set Max Idle instances to > less than 3 (which wouldn't make much sense if you had known you had set min > idle instances to 3), the Admin Console doesn't let you and (unfortunately) > doesn't give a good error as to why. So, you can set it to 3, but as long > as Always-On is still on it won't let you set it to less than that. > > We'll see if we can figure out a way around this... > > Sorry about that! > > Greg -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
