Re: Most popular (view counts), performance and Varnish cache
Hey Oren, Thanks for the comments. I think probing Google Analytics with a DelayedJob is the way to go. Thanks again, Russell. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. 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.
Re: Autoscaling of dynos/workers from within app
Hi Miles, Don't mean to shamelessly plug our product here, but you're use case is so fitting for it. You might want to consider trying the SimpleWorker Add-on so you don't need to scale up your worker threads or anything like that, you just queue up jobs and they'll get run in parallel. Regards, Travis Reeder On Tue, Mar 1, 2011 at 1:51 AM, Miles S. wed...@gmail.com wrote: I'm trying to auto scale my workers and I am using resque instead of DJ. I've tried using the heroku gem, however, when I use any account besides the master account, I get an RestClient::UnprocessableEntity: Unprocessable Entity error. From my testing it appears that collaborators are not able to modify the number of running workers/dynos. I don't want to use my master account, as this project is shared amongst developers, and I don't really want my master account and password being committed to Git for everyone to see. I've also tried finding information on how to use the heroku rest API directly, but have come up with nothing. Is there any way to do what I'm trying to do? -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. 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. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. 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.
App creation failing
Just tried to create a new app and its stuck on Create Status: creating for the last 20 minutes. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. 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.
MongoHQ Connection Issues
The last couple of months we've seen sporadic connection issues from our Heroku app to MongoHQ. It's usually about 10-20 a day, and a typical error looks like this (from Exceptional): VersionsController# (Timeout::Error) execution expired /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:797:in `read' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:797:in `receive_message_on_socket' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:667:in `receive_header' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:657:in `receive' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:435:in `block in receive_message' internal:prelude:10:in `synchronize' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:433:in `receive_message' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:384:in `block in send_initial_query' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:543:in `instrument' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:383:in `send_initial_query' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:348:in `refresh' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:72:in `next_document' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/db.rb:492:in `command' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:636:in `check_is_master' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:455:in `connect' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:512:in `checkout_reader' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:428:in `receive_message' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:384:in `block in send_initial_query' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/connection.rb:543:in `instrument' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:383:in `send_initial_query' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:348:in `refresh' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/cursor.rb:72:in `next_document' /app/065b4f1b-fbaf-40c9-a050-993b7f0765e6/home/.bundle/gems/ruby/1.9.1/gems/mongo-1.2.4/lib/mongo/collection.rb:229:in `find_one' I've been in contact with MongoHQ support regarding this, but they haven't found a solution yet. There's a thread over at their support forums where we try to find the cause for this. If you've experienced the same thing, please join in with your experiences and possible workarounds: http://support.mongohq.com/discussions/problems/233-connection-failure-issues -martin -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com. 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.
