-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
stats: add support for multiple stats handlers in a single client or server #5347
Conversation
Bump. |
Bump again. PTAL. Let me know if there is any problem with the design or idea or code. |
1. Pluralize the variable names for slices 2. Remove the unnecessary ifs 3. Simplify the unit test
@dfawley PTALA. The check-in-loop in stats_test is actually necessary. After graceful shutdown of server, the ConnEnd events might not be counted, and causing the test to fail: https://github.com/grpc/grpc-go/runs/6699361791?check_suite_focus=true . For client-side, the close of channel doesn't mean all processing logic on the client-side is finished, hence the problem. Other renaming or optimizations (remove if) are done. |
The failure is unrelated. |
@dfawley PTALAAA. |
As title.
The user-facing interface is unchanged, but the behavior is slightly different. (We discussed this) If a user application intentionally sets StatsHandler repeatedly and only expects the last one to be effective, we will break them.
RELEASE NOTES: