Skip to content

Conversation

@dapengzhang0
Copy link
Contributor

This is to implement one of changes made in the spec
https://github.com/grpc/proposal/pull/89/files

@CheckForNull
private final ChannelTracer channelTracer;
private final Channelz channelz;
private Boolean nonzeroBackends; // a flag for doing channel tracing when flipped
Copy link
Contributor

@zpencer zpencer Jul 23, 2018

Choose a reason for hiding this comment

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

I think this part would be more clear if we created a separate enum for onAddresses and onError, since the goal is to avoid consecutive reports for the same event type.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Per the new spec, error events in general are not logged unless it results in # of backends down to zero from nonzeor. (Both "zero backends resolved" and "general error" are considered # of backends <- zero). A separate enum for error seems overly specific. Maybe the flag can be refactored as "error"?

Copy link
Contributor

@zpencer zpencer left a comment

Choose a reason for hiding this comment

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

LGTM if we flip the negation

@dapengzhang0 dapengzhang0 merged commit e1865b5 into grpc:master Jul 23, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Oct 21, 2018
@dapengzhang0 dapengzhang0 deleted the channeltrace3 branch May 4, 2020 04:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants