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

Fix some vtctld commands failing to return information to vtctlclient #4647

Merged
merged 1 commit into from
Feb 20, 2019

Conversation

dweitzman
Copy link
Member

Commands need to log to the wrangler logger so grpcvtctlserver can
sent output back over the network instead of just logging locally.

Signed-off-by: David Weitzman [email protected]

Commands need to log to the wrangler logger so grpcvtctlserver can
sent output back over the network instead of just logging locally.

Signed-off-by: David Weitzman <[email protected]>
Copy link
Member

@deepthi deepthi left a comment

Choose a reason for hiding this comment

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

LGTM. I do see that we have a bunch of wr.Logger().Printf in the mix. Any idea what level that prints at?

@dweitzman
Copy link
Member Author

Printf will have level "CONSOLE" from https://github.com/vitessio/vitess/blob/master/proto/logutil.proto, as implemented by

func (cl *CallbackLogger) Printf(format string, v ...interface{}) {

On the client side, https://github.com/vitessio/vitess/blob/master/go/cmd/vtctlclient/main.go#L57 receives the logutil events and asks logutil to write them to a local console logger

@dweitzman dweitzman merged commit b7e5a98 into vitessio:master Feb 20, 2019
@dweitzman dweitzman deleted the fix_wrangler_logging branch February 20, 2019 22:32
frouioui pushed a commit to planetscale/vitess that referenced this pull request Mar 26, 2024
Signed-off-by: Dirkjan Bussink <[email protected]>
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.

2 participants