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.

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

config: disable snapshot syncer by default #2611

Merged
merged 1 commit into from
Dec 26, 2018
Merged

config: disable snapshot syncer by default #2611

merged 1 commit into from
Dec 26, 2018

Conversation

fuweid
Copy link
Contributor

@fuweid fuweid commented Dec 25, 2018

Signed-off-by: Wei Fu fhfuwei@163.com

Ⅰ. Describe what this PR did

The CRI can report the disk usage of contaienr with inode number.
However, the iteration will take long time if the number of files are
too much. Based on this, I think we should disable it by default. If
user wants to use it, set it in config.

Ⅱ. Does this pull request fix one issue?

NONE

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)

no need

Ⅳ. Describe how to verify it

check the log

Ⅴ. Special notes for reviews

The CRI can report the disk usage of contaienr with inode number.
However, the iteration will take long time if the number of files are
too much. Based on this, I think we should disable it by default. If
user wants to use it, set it in config.

Signed-off-by: Wei Fu <fhfuwei@163.com>
@codecov
Copy link

codecov bot commented Dec 25, 2018

Codecov Report

Merging #2611 into master will decrease coverage by 0.63%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2611      +/-   ##
==========================================
- Coverage   69.46%   68.83%   -0.64%     
==========================================
  Files         279      279              
  Lines       18833    18833              
==========================================
- Hits        13083    12964     -119     
- Misses       4281     4394     +113     
- Partials     1469     1475       +6
Flag Coverage Δ
#criv1alpha1test 31.4% <ø> (-0.3%) ⬇️
#criv1alpha2test 35.59% <ø> (-0.58%) ⬇️
#integrationtest 41.07% <ø> (-0.14%) ⬇️
#nodee2etest 32.71% <ø> (-0.52%) ⬇️
#unittest 26.76% <ø> (ø) ⬆️
Impacted Files Coverage Δ
daemon/mgr/snapshot.go 33.33% <0%> (-60.87%) ⬇️
ctrd/snapshot.go 49.09% <0%> (-21.82%) ⬇️
cri/ocicni/cni_manager.go 58.82% <0%> (-11.77%) ⬇️
pkg/streams/utils.go 82.14% <0%> (-9.53%) ⬇️
daemon/mgr/system.go 67.93% <0%> (-5.35%) ⬇️
ctrd/watch.go 80.28% <0%> (-4.23%) ⬇️
daemon/mgr/events.go 96.29% <0%> (-3.71%) ⬇️
ctrd/image.go 76.95% <0%> (-2.18%) ⬇️
ctrd/client.go 68.45% <0%> (-2.02%) ⬇️
cri/v1alpha2/cri.go 67.45% <0%> (-1.86%) ⬇️
... and 7 more

@Ace-Tang
Copy link
Contributor

Will it effect out production ?

@fuweid
Copy link
Contributor Author

fuweid commented Dec 25, 2018

Will it effect our production ?

Not just us, if the container creates a lot of small files and user enables CRI, it will impact the performance and containerd will consume more cpu here.

@zhuangqh zhuangqh merged commit 2ffcfb9 into AliyunContainerService:master Dec 26, 2018
@fuweid fuweid deleted the disable-by-default branch February 21, 2019 03:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants