enhance: set default syncRetryRateLimitDuration to 0s for thinruntime controller #5277
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.



Ⅰ. Describe what this PR does
syncRetryRateLimitDurationis used to avoid frequent status update when fluid's runtime controllers interacts with cache engines (e.g. Alluxio, Jindo, etc.).syncRetryRateLimitDurationdefines the interval where runtime controllers can interact with the cache engine only once.Setting a smaller
syncRetryRateLimitDurationmeans 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, largersyncRetryRateLimitDurationmeans some of the update events would be skipped.This PR sets
syncRetryRateLimitDurationof thinruntime controller to "0s". This is a safe change because ThinRuntime is not designed to have cache engine so no interaction would happen. Setting to0smakes 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