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

[BugFix] Fix shared UDF concurrent load issue #54779

Merged
merged 2 commits into from
Jan 20, 2025

Conversation

wangshisan
Copy link
Contributor

@wangshisan wangshisan commented Jan 7, 2025

Why I'm doing:

If a UDF is created with SHARED mode, suppose the UDF packages would be load only once in a single BE process. While, there is a concurrent issue int the current implementation, which may result in that a shared UDF may be load multiple times when there are concurrent UDF calls.

What I'm doing:

Fixes the concurrent issue, check if the UDF has already been load before load it.

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.4
    • 3.3
    • 3.2
    • 3.1
    • 3.0

@wangshisan wangshisan requested a review from a team as a code owner January 7, 2025 09:06
stdpain
stdpain previously approved these changes Jan 7, 2025
@@ -262,7 +262,9 @@ Status UserFunctionCache::_load_cache_entry(const std::string& url, UserFunction
RETURN_IF_ERROR(_download_lib(url, entry));
}

RETURN_IF_ERROR(_load_cache_entry_internal(url, entry, loader));
if (!entry->is_loaded.load()) {
RETURN_IF_ERROR(_load_cache_entry_internal(entry, loader));
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
RETURN_IF_ERROR(_load_cache_entry_internal(entry, loader));
RETURN_IF_ERROR(_load_cache_entry_internal(url, entry, loader));

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

@wangshisan wangshisan force-pushed the fix_concurrent_udf_load branch from a39df69 to 359231c Compare January 16, 2025 02:45
Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 2 / 2 (100.00%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 be/src/runtime/user_function_cache.cpp 2 2 100.00% []

@Seaven Seaven merged commit f451b65 into StarRocks:main Jan 20, 2025
45 checks passed
Copy link

@Mergifyio backport branch-3.4

@github-actions github-actions bot removed the 3.4 label Jan 20, 2025
Copy link
Contributor

mergify bot commented Jan 20, 2025

backport branch-3.4

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jan 20, 2025
Signed-off-by: ganggewang <[email protected]>
(cherry picked from commit f451b65)
wanpengfei-git pushed a commit that referenced this pull request Feb 14, 2025
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.

3 participants