Thanks, Daniel. I did send a support ticket and they reported back (after I reached out to this forum) that my Postgres host was having chronic OOM errors. The appropriate action was to migrate the database to another host (via follow/promote since it's a Crane instance).
On May 30, 2013, at 4:51 AM, heroku@googlegroups.com wrote: > Today's Topic Summary > Group: http://groups.google.com/group/heroku/topics > > Out of Memory Errors on Simple Queries that Worked Previously [2 Updates] > Problem adding memcache addon [3 Updates] > Out of Memory Errors on Simple Queries that Worked Previously > Jack Royal-Gordon <jac...@pobox.com> May 29 11:47PM -0700 > > Tonight, I started getting "out of memory" errors from several different > queries, many of which are simple, and all of which have worked well in the > past. For example, a simple "select" across several hundred rows that should > produce 20 rows or less gets this error. App has not been touched in several > days, the queries in question have been running regularly for months. The > database is 9.2, upgraded from 9.1 last week, and all queries have run > successfully since the database was upgraded. > > My thought is that the database server needs to be stopped and restarted, but > I don't know how to do that on Heroku. Any ideas? > > Daniel Farina <dan...@heroku.com> May 29 11:53PM -0700 > > > Tonight, I started getting "out of memory" errors from several different > > queries, many of which are simple, and all of which have worked well in the > > past. For example, a simple "select" across several hundred rows that > > should produce 20 rows or less gets this error. App has not been touched in > > several days, the queries in question have been running regularly for > > months. The database is 9.2, upgraded from 9.1 last week, and all queries > > have run successfully since the database was upgraded. > > > My thought is that the database server needs to be stopped and restarted, > > but I don't know how to do that on Heroku. Any ideas? > > This one might be best for a support ticket. There are several > possible causes, but they will likely require closer investigation and > exchange of details that are probably not best done via public list. > Please reference this thread (link: > https://groups.google.com/forum/?fromgroups#!topic/heroku/4qxst42Bq9Q) > and mention that I requested you do that. > > Unless one has started leaking connections, it's reasonably unlikely > that this change is intrinsically 9.2 related. > > Problem adding memcache addon > la...@artsymail.com May 29 02:48PM -0700 > > Hello, > > I am attempting to add memcache to my heroku app, and I received the > following error: > > "The memcache add-on has been disabled. Please choose an alternative > service at https://addons.heroku.com/#caching"; > > I don't see any information on the heroku site about this change, nor are > there any google results for the error. If the memcache add-on is indeed no > longer available, I'll look into memcachier, but if I'm receiving this > error because of a mistake on my part, I'd like to correct it to get > memache running. > > Any help is greatly appreciated! > > Thanks, > Laura > > Daniel Farina <dan...@fdr.io> May 29 02:53PM -0700 > > > longer available, I'll look into memcachier, but if I'm receiving this error > > because of a mistake on my part, I'd like to correct it to get memache > > running. > > Yup, it's no longer available. That add-on decided to cease its > operation. One will have to go elsewhere for their memcache hosting > needs. > > Looks like there is some out of date documentation, though: > > https://devcenter.heroku.com/articles/memcache > > That documentation seems to be maintained by Couchbase, which is the > aforementioned party that deprecated the addon, so Heroku may want to > be looped in as to possibly salvage parts of the document that are > still useful but stop it from indicating that the memcache addon is > still available. > > Daniel Doubrovkine <dbl...@dblock.org> May 29 05:58PM -0400 > > Can we please have an update from Heroku on whether we need to migrate to > someone else's addon ASAP, too, before the addon decides to stop responding > to memcache read/writes? :) > > > -- > > dB. | Moscow - Geneva - Seattle - New York > code.dblock.org - @dblockdotorg <http://twitter.com/#!/dblockdotorg> - > artsy.net - github/dblock <https://github.com/dblock> > > You received this message because you are subscribed to the Google Group > heroku. > You can post via email. > To unsubscribe from this group, send an empty message. > For more options, visit this group. > > -- > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "Heroku Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to heroku+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups "Heroku Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
