Skip to content

Conversation

@TrafalgarZZZ
Copy link
Member

Ⅰ. Describe what this PR does

syncRetryRateLimitDuration is used to avoid frequent status update when fluid's runtime controllers interacts with cache engines (e.g. Alluxio, Jindo, etc.). syncRetryRateLimitDuration defines the interval where runtime controllers can interact with the cache engine only once.

Setting a smaller syncRetryRateLimitDuration means more frequent updates and more interactions with the cache engine. That usually means runtime status (e.g. cached, cached percentage, etc.) might be synced in a more frequent way. However, larger syncRetryRateLimitDuration means some of the update events would be skipped.

This PR sets syncRetryRateLimitDuration of thinruntime controller to "0s". This is a safe change because ThinRuntime is not designed to have cache engine so no interaction would happen. Setting to 0s makes ThinRuntime controller to reconcile all update events without skipping, and this is very important when using ThinRuntime with dynamic mount feature.

Ⅱ. Does this pull request fix one issue?

NONE

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

… controller

Signed-off-by: trafalgarzzz <trafalgarz@outlook.com>
@sonarqubecloud
Copy link

@codecov
Copy link

codecov bot commented Oct 11, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.70%. Comparing base (f8caa97) to head (4efba6d).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #5277   +/-   ##
=======================================
  Coverage   56.70%   56.70%           
=======================================
  Files         440      440           
  Lines       30369    30369           
=======================================
  Hits        17220    17220           
  Misses      11537    11537           
  Partials     1612     1612           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@cheyang cheyang requested a review from Syspretor October 12, 2025 03:46
@Syspretor
Copy link
Collaborator

/lgtm
/approve

@fluid-e2e-bot
Copy link

fluid-e2e-bot bot commented Oct 12, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Syspretor
Once this PR has been reviewed and has the lgtm label, please ask for approval from trafalgarzzz by writing /assign @trafalgarzzz in a comment. For more information see:The Kubernetes Code Review Process.

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

Details 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

@RongGu RongGu merged commit 2cfd799 into fluid-cloudnative:master Oct 12, 2025
15 of 16 checks passed
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.

3 participants