Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Merge requests
  • !7727

Closed
Created Sep 10, 2014 by Administrator@rootOwner
  • Report abuse
Report abuse

change unicorn timeout to 300

  • Overview 8
  • Commits 1
  • Changes 1

Created by: bbodenmiller

I'm not entirely sure this is necessary however I've been getting lots of 502 errors recently that seem to relate to timeout values. Can someone elaborate on what other things could be affected by this timeout value being low or high?

Can someone explain why the Unicorn timeout does not match the nginix proxy_connect_timeout?

Additionally can someone explain satellites -> timeout in gitlab/yml?

/cc @Razer6 @randx @dosire

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/bbodenmiller/patch-3