fix(apigateway): set GOMAXPROCS to 2 when executing climc #22009
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
k3s 部署的节点默认会设置 pod pid limit 到 1024 限制一个容器能启动的线程总数，climc pod 在多核的宿主机上运行时，go runtime 会根据 ncpu 启动很多线程来运行 goroutine ，就会出现
fatal error: newosproc的错误Does this PR need to be backport to the previous release branch?:
/area apigateway
/cc @swordqiu @wanyaoqi @ioito