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

Support to configure the cache size of vineyard fuse #3982

Merged

Conversation

dashanji
Copy link
Contributor

Ⅰ. Describe what this PR does

Part of #3749

Copy link

fluid-e2e-bot bot commented Apr 26, 2024

Hi @dashanji. Thanks for your PR.

I'm waiting for a fluid-cloudnative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@@ -76,6 +76,8 @@ spec:
value: {{ .Values.fuse.targetPath }}/rpc-conf
- name: PRESTOP_MARKER
value: /tmp/prestop-marker
- name: CACHE_SIZE
Copy link
Collaborator

Choose a reason for hiding this comment

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

How about using

{{- if .Values.fuse.options.cacheSize }}
- name: CACHE_SIZE
  value: "{{ .Values.fuse.options.cacheSize }}"
{{- end }}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I used a range to avoid specifying each argument one by one.

// options:
// cache-size: "0"
// +optional
Options map[string]string `json:"options,omitempty"`
Copy link
Collaborator

Choose a reason for hiding this comment

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

How to handle other options? I think they are the parts of command and args.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the advice. I have used a range to iterate all fuse options.

// options:
// cache-size: "0"
// +optional
Options map[string]string `json:"options,omitempty"`
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

I also believe that the name VineyardClientSocketSpec would be more appropriate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

@dashanji dashanji force-pushed the configure-vineyard-fuse-cache branch 3 times, most recently from 143e40d to b45eb4b Compare April 28, 2024 08:42
Copy link

codecov bot commented Apr 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.35%. Comparing base (6d0ba26) to head (b45eb4b).
Report is 91 commits behind head on master.

Current head b45eb4b differs from pull request most recent head 1e31e3b

Please upload reports for the commit 1e31e3b to get more accurate results.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3982      +/-   ##
==========================================
+ Coverage   64.33%   64.35%   +0.02%     
==========================================
  Files         477      477              
  Lines       28444    28456      +12     
==========================================
+ Hits        18300    18314      +14     
+ Misses       7968     7967       -1     
+ Partials     2176     2175       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@cheyang
Copy link
Collaborator

cheyang commented Apr 30, 2024

@TrafalgarZZZ Please also take a look. Thanks.

@dashanji dashanji force-pushed the configure-vineyard-fuse-cache branch from b45eb4b to 1e31e3b Compare May 21, 2024 11:53
Copy link

sonarcloud bot commented May 21, 2024

Quality Gate Passed Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
11.3% Duplication on New Code

See analysis details on SonarCloud

Copy link
Collaborator

@cheyang cheyang left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

Copy link

fluid-e2e-bot bot commented May 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cheyang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@fluid-e2e-bot fluid-e2e-bot bot merged commit c92c650 into fluid-cloudnative:master May 27, 2024
8 checks passed
@dashanji dashanji deleted the configure-vineyard-fuse-cache branch June 5, 2024 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants