Skip to content

Conversation

@fuweid
Copy link
Member

@fuweid fuweid commented Aug 13, 2022

It is follow-up of #7254. This commit will increase ReadHeaderTimeout
from 3s to 30m, which prevent from unexpected timeout when the node is
running with high-load. 30 Minutes is longer enough to get close to
before what #7254 changes.

And ideally, we should allow user to configure the streaming server if
the users want this feature.

Align with https://github.com/containerd/project/blob/main/script/validate/template/go.txt.

cc @mxpv and @mikebrow

@fuweid fuweid changed the title Follow up #7254 Follow up #7254 (Switch to Go 1.19) Aug 13, 2022
@dcantah
Copy link
Member

dcantah commented Aug 13, 2022

Was hoping it wasn't something in my change, but looks like gopkg is out to lunch indeed

go: gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v2": reading https://gopkg.in/yaml.v2?go-get=1: 502 Bad Gateway
	server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

@zouyee
Copy link
Contributor

zouyee commented Aug 14, 2022

Was hoping it wasn't something in my change, but looks like gopkg is out to lunch indeed

go: gopkg.in/[email protected]: unrecognized import path "gopkg.in/yaml.v2": reading https://gopkg.in/yaml.v2?go-get=1: 502 Bad Gateway
	server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

#7287 (comment)

@dcantah
Copy link
Member

dcantah commented Aug 16, 2022

@fuweid Can rebase now that the CI should be back in order

@fuweid
Copy link
Member Author

fuweid commented Aug 17, 2022

@fuweid Can rebase now that the CI should be back in order

For sure. Updated

fuweid added 2 commits August 18, 2022 07:42
It is follow-up of containerd#7254. This commit will increase ReadHeaderTimeout
from 3s to 30m, which prevent from unexpected timeout when the node is
running with high-load. 30 Minutes is longer enough to get close to
before what containerd#7254 changes.

And ideally, we should allow user to configure the streaming server if
the users want this feature.

Signed-off-by: Wei Fu <[email protected]>
@fuweid
Copy link
Member Author

fuweid commented Aug 18, 2022

// Vagrant BOX:rockylinux/8
=== Failed
    default: === FAIL: . TestShimOOMScore (0.07s)
    default:     container_linux_test.go:1441: failed to start shim: start failed: io.containerd.runc.v2: failed to join cgroup /containerd/oomshim: write /sys/fs/cgroup/cpu/containerd/oomshim/cgroup.procs: invalid argument: exit status 1: unknown

Hmm.

Copy link
Member

@estesp estesp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants