Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Connections are kept alive even after the request is served #86

Closed
ibnesayeed opened this issue Jun 9, 2016 · 2 comments
Closed

Connections are kept alive even after the request is served #86

ibnesayeed opened this issue Jun 9, 2016 · 2 comments
Labels
bug
Milestone
1.0-RC6

Comments

@ibnesayeed
Copy link
Member

This can unnecessarily keep unused connections with upstream archives.
@ibnesayeed ibnesayeed added the bug label Jun 9, 2016
@ibnesayeed
Copy link
Member Author

This needs further investigation.

@ibnesayeed ibnesayeed reopened this Jun 9, 2016
@ibnesayeed
Copy link
Member Author

Now we are using two new Transport fields IdleConnTimeout and MaxIdleConns introduced in Go 1.7 to address this issue. This changes the minimum version of Go to build MemGator.

ibnesayeed added a commit that referenced this issue Aug 2, 2016
@ibnesayeed
Go version requirement for build changed, #86
5b833af
ibnesayeed added a commit that referenced this issue Aug 2, 2016
@ibnesayeed
Explicit Go version in Dockerfile, #86
f416ae3
@ibnesayeed ibnesayeed modified the milestone: 1.0-RC6 Aug 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.0-RC6
Development

No branches or pull requests
1 participant
@ibnesayeed