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

core: added changes to make service config more explicit by logging required info #11917

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

vinodhabib
Copy link
Contributor

@vinodhabib vinodhabib commented Feb 21, 2025

core: added changes to make service config more explicit by logging required details of transported JSON

Fixes: #5758

@vinodhabib vinodhabib marked this pull request as ready for review February 25, 2025 07:18
@shivaspeaks shivaspeaks added the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Feb 26, 2025
@grpc-kokoro grpc-kokoro removed the kokoro:run Add this label to a PR to tell Kokoro the code is safe and tests can be run label Feb 26, 2025
InternalConfigSelector prevConfig = configSelector.get();
configSelector.set(config);
configSelector.set(newConfig);
channelLogger.log(ChannelLogLevel.INFO,
Copy link
Member

@shivaspeaks shivaspeaks Mar 3, 2025

Choose a reason for hiding this comment

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

This could be right but this can also lead to spamming as config update can happen per RPC.

Perhaps we should discuss/ rethink on the requirement for this logging. Or maybe it will be better if we log only when default config is applied and expected retry config is not applied when retry is enabled and service config is present. And we also need to figure out how it will help the user, about why the given config was not applied! Logging that will be much better.

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.

Make service config more explicit
3 participants