StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POStrange request timeout on Heroku
primarykey
Id
7601497
data
AcceptedAnswerId
12182949
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-29T18:05:12.113
FavoriteCount
0
LastActivityDate
2012-08-29T16:58:44.673
LastEditDate
2012-08-16T03:30:32.040
LastEditorUserId
28037
OwnerUserId
166918
ParentId
0
PostTypeId
1
Score
0
ViewCount
933
LastEditorDisplayName
text
Body
First of all I'm quite familiar with the H12 timeouts on Heroku. I use Delayed Job for long running tasks, etc. The issue I'm seeing is that a rails 3 request that takes 2 seconds locally, is timing out on Heroku. I've added logging for the entirety of the controller action, and both locally and on heroku the code execution takes about 2 seconds. Example from Heroku: <pre><code>2011-09-28T20:06:43+00:00 app[web.2]: Started POST "/xyz" for 69.181.51.78 at Wed Sep 28 13:06:43 -0700 2011 2011-09-28T20:07:12+00:00 app[web.2]: ***saved in 0.027939 seconds 2011-09-28T20:07:12+00:00 app[web.2]: ***split in 0.006164 seconds 2011-09-28T20:07:12+00:00 app[web.2]: ***reject in 0.017268 seconds 2011-09-28T20:07:12+00:00 app[web.2]: ***validate in 0.029043 seconds 2011-09-28T20:07:13+00:00 heroku[router]: Error H12 (Request timeout) -> POST xyz.com/xyz dyno=web.2 queue= wait= service=30000ms status=503 bytes=0 2011-09-28T20:07:13+00:00 app[web.2]: ***duped in 0.561905 seconds 2011-09-28T20:07:13+00:00 app[web.2]: ***dropped cats in 0.005318 seconds 2011-09-28T20:07:14+00:00 app[web.2]: ***added in 0.148055 seconds 2011-09-28T20:07:14+00:00 app[web.2]: ***saved in 0.245283 seconds 2011-09-28T20:07:14+00:00 app[web.2]: ***handled in 1.721555 seconds </code></pre> As you can see from the last line, according to the logging the whole process takes 1.7 seconds, but none of these log lines are showing up for 29 seconds (we're using Rack.Timeout and set it to 29 seconds) The request is a fairly large POST about 72K, and that ***dup log line I'm duping a hash that is about the same size. Is it possible I'm hitting the Heroku memory limit and that would manifest as an H12 timeout?
Tags
<ruby-on-rails><memory><heroku><timeout>
Title
Strange request timeout on Heroku
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USculix
UserOwnerUserId
1. USNader
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POStrange request timeout on Heroku
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.