Skip to content

刷新服务时,不重启服务(依赖grpc-go项目升级支持)#96

Open
ssfyn wants to merge 1 commit intodubbogo:mainfrom
ssfyn:hotfix/refresh-service
Open

刷新服务时,不重启服务(依赖grpc-go项目升级支持)#96
ssfyn wants to merge 1 commit intodubbogo:mainfrom
ssfyn:hotfix/refresh-service

Conversation

@ssfyn
Copy link

@ssfyn ssfyn commented Jun 25, 2025

What this PR does:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


Summary by CodeRabbit

  • Refactor
    • Improved the service refresh process to update service registrations on the existing server without restarting or recreating the server or listener. This results in a smoother and more efficient refresh experience for users.

@coderabbitai
Copy link

coderabbitai bot commented Jun 25, 2025

Walkthrough

The RefreshService method in the TripleServer was updated to register services directly on the existing gRPC server instance instead of creating a new server, stopping the old one, and restarting with a new listener. The reflection service now references the current server, and all logic related to server recreation was removed.

Changes

File(s) Change Summary
pkg/triple/dubbo3_server.go Refactored RefreshService to register services on the existing gRPC server without restarting.

Poem

A server once stopped, then started anew,
Now simply refreshes—no need to redo!
With listeners steady and services bright,
The code hops forward, everything’s right.
A rabbit approves, with a twitch of delight! 🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 339a5a6 and ee41140.

📒 Files selected for processing (1)
  • pkg/triple/dubbo3_server.go (1 hunks)
🔇 Additional comments (2)
pkg/triple/dubbo3_server.go (2)

296-296: LGTM: Reflection service server reference updated correctly.

The reflection service's gRPC server reference is properly updated to use the existing server instance, which aligns with the refresh-without-restart approach.


283-300: ```shell
#!/bin/bash
set -euo pipefail

Search for RegisterService definitions in the cloned grpc-go repo

echo "=== Searching for RegisterService definitions ==="
grep -R -n "func .*RegisterService" /tmp/grpcgo

If found, display each definition with context

echo -e "\n=== Context around each RegisterService definition ==="
grep -R -n "func .*RegisterService" /tmp/grpcgo | while IFS=: read -r path line rest; do
echo "--- $path:$line ---"
sed -n "$((line-5)),$((line+20))p" "$path"
done


</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

desc := grpcService.XXX_ServiceDesc()
desc.ServiceName = key.(string)
grpcServer.RegisterService(desc, value)
t.grpcServer.RegisterService(desc, value)
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add error handling for service registration failures.

The RegisterService calls lack error handling, which could lead to silent failures during service refresh.

Add error handling and logging:

 grpcService, ok := value.(common.TripleGrpcService)
 if ok {
     desc := grpcService.XXX_ServiceDesc()
     desc.ServiceName = key.(string)
-    t.grpcServer.RegisterService(desc, value)
+    if err := t.grpcServer.RegisterService(desc, value); err != nil {
+        t.opt.Logger.Errorf("Failed to register gRPC service %s: %v", key.(string), err)
+        return true
+    }
 } else {
     desc := createGrpcDesc(key.(string), value.(common.TripleUnaryService))
-    t.grpcServer.RegisterService(desc, value)
+    if err := t.grpcServer.RegisterService(desc, value); err != nil {
+        t.opt.Logger.Errorf("Failed to register unary service %s: %v", key.(string), err)
+        return true
+    }
 }

Also applies to: 293-293

🤖 Prompt for AI Agents
In pkg/triple/dubbo3_server.go at lines 290 and 293, the calls to
t.grpcServer.RegisterService do not handle errors, risking silent failures
during service refresh. Modify these calls to capture the returned error, check
if it is non-nil, and log an appropriate error message to ensure any
registration failure is detected and reported.

⚠️ Potential issue

Critical: Prevent duplicate service registration to avoid runtime panics.

Calling RegisterService on an already registered service typically causes a panic in gRPC. The code should check if services are already registered before attempting re-registration.

Consider implementing duplicate registration prevention:

 t.rpcServiceMap.Range(func(key, value interface{}) bool {
+   // Skip if already registered to prevent duplicate registration panic
+   if t.registeredKey[key.(string)] {
+       return true
+   }
+   t.registeredKey[key.(string)] = true
+   
    grpcService, ok := value.(common.TripleGrpcService)
    if ok {
        desc := grpcService.XXX_ServiceDesc()
        desc.ServiceName = key.(string)
        t.grpcServer.RegisterService(desc, value)
    } else {
        desc := createGrpcDesc(key.(string), value.(common.TripleUnaryService))
        t.grpcServer.RegisterService(desc, value)
    }

Also applies to: 293-293

🤖 Prompt for AI Agents
In pkg/triple/dubbo3_server.go at lines 290 and 293, the code calls
RegisterService without checking if the service is already registered, which can
cause runtime panics. To fix this, add a check before each RegisterService call
to verify if the service has already been registered on the grpcServer, and only
call RegisterService if it is not registered yet. This prevents duplicate
registration and avoids panics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant