Upcoming maintenance notification

6 views
Skip to first unread message

Ikai L (Google)

unread,
Jun 30, 2010, 2:51:23 PM6/30/10
to google-a...@googlegroups.com
Hey guys,

I just wanted to point out there are upcoming maintenance periods scheduled for July 7th and July 14th at 5pm Pacific. More details here:


Normally, I wouldn't post these notifications to this group, as they belong in the "downtime notify" group, however, users are reporting that this message went into their spam folder. Can anyone verify this, or let me know in this thread if this message was correctly delivered?

If you want to be notified of upcoming maintenance periods, make sure to join this group: 


We're doing our best to minimize these periods in the future, but there are times when these periods will be absolutely necessary.

--
Ikai Lan 
Developer Programs Engineer, Google App Engine

johntray

unread,
Jun 30, 2010, 3:19:14 PM6/30/10
to Google App Engine
I can confirm that the email from the downtime-notify group was indeed
routed to my Gmail spam folder. It includes a red-overlay message:
"Warning: This message may not be from whom it claims to be. Beware of
following any links in it or of providing the sender with any personal
information". There is also a link to "Learn more" which points to
http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=8253.

Thanks for posting here, as I would have completely missed it





On Jun 30, 2:51 pm, "Ikai L (Google)" <ika...@google.com> wrote:
> Hey guys,
>
> I just wanted to point out there are upcoming maintenance periods scheduled
> for July 7th and July 14th at 5pm Pacific. More details here:
>
> http://groups.google.com/group/google-appengine-downtime-notify/brows...

Robert Kluin

unread,
Jun 30, 2010, 3:48:33 PM6/30/10
to google-a...@googlegroups.com
Went to my spam folder as well.

> --
> 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-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>

Ikai L (Google)

unread,
Jun 30, 2010, 3:55:30 PM6/30/10
to google-a...@googlegroups.com
Was this message correctly directed into anyone's inbox?

Claude Vedovini

unread,
Jun 30, 2010, 4:46:54 PM6/30/10
to Google App Engine
Same here!

On Jun 30, 9:19 pm, johntray <john.tur...@gmail.com> wrote:
> I can confirm that the email from the downtime-notify group was indeed
> routed to my Gmail spam folder. It includes a red-overlay message:
> "Warning: This message may not be from whom it claims to be. Beware of
> following any links in it or of providing the sender with any personal
> information". There is also a link to "Learn more"  which points tohttp://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=8253.

nickmilon

unread,
Jun 30, 2010, 5:58:28 PM6/30/10
to Google App Engine
Same for me ;-)

Darien Caldwell

unread,
Jun 30, 2010, 7:56:26 PM6/30/10
to Google App Engine
Oddly enough, yes. I got the message in my Inbox, with no issues.

Luís Marques

unread,
Jun 30, 2010, 9:25:30 PM6/30/10
to Google App Engine
Same here, in the spam folder marked as fishing.

Luís

Takashi MATSUO

unread,
Jun 30, 2010, 10:05:28 PM6/30/10
to google-a...@googlegroups.com
Unfortunately same here. The message went to the spam folder with the

message "Warning: This message may not be from whom it claims to be.
Beware of following any links in it or of providing the sender with
any personal information. ".

--
Takashi Matsuo
matsuo....@gmail.com
Kay's daddy

2010/7/1 Luís Marques <luism...@gmail.com>:


> Same here, in the spam folder marked as fishing.
>
> Luís
>

Arun Shanker Prasad

unread,
Jun 30, 2010, 11:34:03 PM6/30/10
to Google App Engine
Yup, the downtime notification mail was in my inbox.

On Jul 1, 12:55 am, "Ikai L (Google)" <ika...@google.com> wrote:
> Was this message correctly directed into anyone's inbox?
>
> On Wed, Jun 30, 2010 at 12:48 PM, Robert Kluin <robert.kl...@gmail.com>wrote:
>
>
>
>
>
> > Went to my spam folder as well.
>
> > google-appengi...@googlegroups.com<google-appengine%2Bunsubscrib e...@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-a...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com<google-appengine%2Bunsubscrib e...@googlegroups.com>
> > .

Ikai L (Google)

unread,
Jul 1, 2010, 2:28:37 PM7/1/10
to google-a...@googlegroups.com
Thanks for the feedback, guys. We figured out what was causing this. Upcoming notifications on that list will come from my email address temporarily until we resolve this.

To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

Greg

unread,
Jul 1, 2010, 6:40:01 PM7/1/10
to Google App Engine
The message was in my spam box, and I moved it to my inbox yesterday.
It has now disappeared completely!
> > > > google-appengi...@googlegroups.com<google-appengine%2Bunsu...@googlegroups.com><google-appengine%2Bunsubscrib
> > e...@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-a...@googlegroups.com
> > .
> > > > To unsubscribe from this group, send email to
> > > > google-appengi...@googlegroups.com<google-appengine%2Bunsu...@googlegroups.com><google-appengine%2Bunsubscrib
> > e...@googlegroups.com>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/google-appengine?hl=en.
>
> > > --
> > > Ikai Lan
> > > Developer Programs Engineer, Google App Engine
> > > Blog:http://googleappengine.blogspot.com
> > > Twitter:http://twitter.com/app_engine
> > > Reddit:http://www.reddit.com/r/appengine
>
> > --
> > 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-a...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com<google-appengine%2Bunsu...@googlegroups.com>

Jan Z

unread,
Jul 4, 2010, 12:45:40 AM7/4/10
to Google App Engine
The last scheduled outages were arranged during the weekend - this
made life a great deal easier, particularly as the Capability API
wasn't working etc.

Could we please aim to keep outages to weekends until we've gone
through a couple without any hitches?

Thanks!

J

On Jul 1, 6:51 am, "Ikai L (Google)" <ika...@google.com> wrote:
> Hey guys,
>
> I just wanted to point out there are upcoming maintenance periods scheduled
> for July 7th and July 14th at 5pm Pacific. More details here:
>
> http://groups.google.com/group/google-appengine-downtime-notify/brows...

Viðar Svansson

unread,
Jul 6, 2010, 7:54:21 AM7/6/10
to google-a...@googlegroups.com
Hi

It would be nice if AppEngine would post a message to our apps before
it enters maintenance mode and again when it resumes to normal
operation mode. This would allow us to disable features that require
writing to the datastore. I realize we can catch the capability
exceptions but that means we need to try to write first, which is not
good enough IMO.

Regards,
Viðar

> --
> 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-a...@googlegroups.com.

> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.

Barry Hunter

unread,
Jul 6, 2010, 8:20:22 AM7/6/10
to google-a...@googlegroups.com
But what would you do with the notification? 

You can't put it in memcache (memcache is usually disabled too) and, trying to put it in the datastore (provided you can do it before it actully goes read-only), will probably be no more efficient than trying a real write anyway. 

But that does lead to possibly a quick way to test, try a Memcache set. 

"will instead return False for set() calls ..... In addition, memcache API calls will return immediately during this period, without any additional latency."


2010/7/6 Viðar Svansson <vidar...@gmail.com>

Viðar Svansson

unread,
Jul 6, 2010, 9:55:13 AM7/6/10
to google-a...@googlegroups.com
The notification would be sent before it enters read-only state so
there is time to save data as you assumed.
We could write the capability state to a three layered cache (memory,
memcache, and datastore).

But like you said, there are other ways to check this during a r-o
mode and a quick memcache put might be the best way. I haven't
research what is the optimal approach here.
Regardless, that does not help us if we need to perform some work
before entering r-o mode.

Let's say that the notification is sent one hour in advance. Then we
might want to:
* Prioritize critical background processing work so it completes
before the deadline.
* Disable non-essential work to minimize overall workload when the app
enters r-o mode.
* Notify our users that our app will soon enter a r-o state and that
features will be disabled.
* Notify developers that missed the email for some reason (gmail
marked it as spam, etc).
* If the app is a service, notify other apps that it is to go offline.

Of course, it would also help if the notification included an
estimation of the downtime.

Given the frequent downtimes, it is essential that there is a way to
handle them more gracefully than the current approach allows. At least
if we want to build non-toy apps.

- Viðar

Michael Shen

unread,
Jul 9, 2010, 1:32:49 AM7/9/10
to Google App Engine
ello..

Can somebody help me ? I found that my app (Application ID:
dynamicpathfind) didn't work properly since the maintenance
yesterday.It still can't work properly now!!!
I didn't change any of my code,but now,when i requset a
service, it seems to spend more time to response than before . When
the heavy load task is requested (it can work correctly before the
maintenance) , it caused "DeadlineExceededError" .
Here are the info shown by the app engine:

<class 'google.appengine.runtime.DeadlineExceededError'>:
Traceback (most recent call last):
File "/base/data/home/apps/dynamicpathfind/2.343233095557591169/
main.py", line 557, in main
run_wsgi_app(app)
File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/webapp/util.py", line 97, in run_wsgi_app
run_bare_wsgi_app(add_wsgi_middleware(application))
File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/webapp/util.py", line 115, in run_bare_wsgi_app
result = application(env, _start_response)
File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/webapp/__init__.py", line 513, in __call__
handler.post(*groups)
File "/base/data/home/apps/dynamicpathfind/2.343233095557591169/
main.py", line 228, in post
self.findpath(self.withoutflow)
File "/base/data/home/apps/dynamicpathfind/2.343233095557591169/
main.py", line 338, in findpath
nh = self.manhattan(neighbor)
File "/base/data/home/apps/dynamicpathfind/2.343233095557591169/
main.py", line 266, in manhattan
for q in msg:
File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/db/__init__.py", line 1685, in __iter__
return self.run()
File "/base/python_runtime/python_lib/versions/1/google/appengine/
ext/db/__init__.py", line 1669, in run
iterator = raw_query.Run(rpc=rpc)
File "/base/python_runtime/python_lib/versions/1/google/appengine/
api/datastore.py", line 1148, in Run
return self._Run(**kwargs)
File "/base/python_runtime/python_lib/versions/1/google/appengine/
api/datastore.py", line 1177, in _Run
datastore_pb.QueryResult(), rpc)
File "/base/python_runtime/python_lib/versions/1/google/appengine/
api/datastore.py", line 192, in _MakeSyncCall
rpc.wait()
File "/base/python_runtime/python_lib/versions/1/google/appengine/
api/apiproxy_stub_map.py", line 460, in wait
self.__rpc.Wait()
File "/base/python_runtime/python_lib/versions/1/google/appengine/
api/apiproxy_rpc.py", line 112, in Wait
rpc_completed = self._WaitImpl()
File "/base/python_runtime/python_lib/versions/1/google/appengine/
runtime/apiproxy.py", line 108, in _WaitImpl
rpc_completed =
_apphosting_runtime___python__apiproxy.Wait(self)<class
'google.appengine.runtime.DeadlineExceededError'>:
------------------------------------------------------------------------------------------------------------------------
Can somebody give me a help ? Is the problem cauesd by latency ? or
there was some changes after the maintenance ?
How can i fix it ?

B.T.W.: my English is so poor .sorry
> > 2010/7/6 Viðar Svansson <vidarsv...@gmail.com>
>
> >> Hi
>
> >> It would be nice if AppEngine would post a message to our apps before
> >> it enters maintenance mode and again when it resumes to normal
> >> operation mode. This would allow us to disable features that require
> >> writing to the datastore. I realize we can catch the capability
> >> exceptions but that means we need to try to write first, which is not
> >> good enough IMO.
>
> >> Regards,
> >> Viðar
>
> >http://groups.google.com/group/google-appengine?hl=en.- 隱藏被引用文字 -
>
> - 顯示被引用文字 -
Reply all
Reply to author
Forward
0 new messages