Skip to content

Review and communicate server timeout policies #19

@jar398

Description

@jar398

Sometimes API calls can run for a long time. We don't want to let them run arbitrarily long, because that is potentially forever, consuming server resources uselessly. My current understanding of what happens in this case is:

  • nginx has a timeout, I don't know what it is. If a rails call takes longer than that, then I'm not sure what it does - does nginx have a way to abort the rails call, or does rails keep trying to complete the call even though nginx has already delivered a failing HTTP response to the client?
  • rails has its own timeout, I don't know what it is.

I think that ideally the nginx timeout is the same as the rails timeout. Perhaps this is already the case - but I would be more relaxed if someone could check this for me.

And if I were to learn what the timeout is, I could put it in the API documentation and/or tell our alpha testers what it is, so I would like to request this as well.

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions