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

Upgraded OTel to 0.20.0 #2807

Closed
wants to merge 3 commits into from

Conversation

joe-elliott
Copy link
Member

Which problem is this PR solving?

  • Upgrades OTel to the latest release

Short description of the changes

  • Copied generateAndRegisterManualResolver from the "google.golang.org/grpc/resolver/manual" package. This appears to be a test function we are using to init the resolver? Unsure why this was used.
  • Removed all reference to the queued_retry processor as it no longer exists.
  • The Status object can no longer be nil. Adjusted code accordingly.

Signed-off-by: Joe Elliott <[email protected]>
@joe-elliott joe-elliott requested a review from a team as a code owner February 10, 2021 20:22
@joe-elliott joe-elliott requested a review from vprithvi February 10, 2021 20:22
@mergify mergify bot requested a review from jpkrohling February 10, 2021 20:23
@codecov
Copy link

codecov bot commented Feb 10, 2021

Codecov Report

Merging #2807 (3d86d58) into master (d23b3e2) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2807   +/-   ##
=======================================
  Coverage   95.95%   95.95%           
=======================================
  Files         218      218           
  Lines        9620     9624    +4     
=======================================
+ Hits         9231     9235    +4     
  Misses        322      322           
  Partials       67       67           
Impacted Files Coverage Δ
cmd/agent/app/reporter/grpc/builder.go 96.15% <100.00%> (+0.32%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d23b3e2...e0650ee. Read the comment docs.

yurishkuro
yurishkuro previously approved these changes Feb 10, 2021
@@ -80,7 +82,7 @@ func (b *ConnBuilder) CreateConnection(logger *zap.Logger, mFactory metrics.Fact
return nil, errors.New("at least one collector hostPort address is required when resolver is not available")
}
if len(b.CollectorHostPorts) > 1 {
r, _ := manual.GenerateAndRegisterManualResolver()
r := generateAndRegisterManualResolver()
Copy link
Member

Choose a reason for hiding this comment

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

is it preemptive change needed to upgrade grpc later?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's due to the otel grpc dependency upgrading here:
https://github.com/jaegertracing/jaeger/pull/2807/files#diff-c941bfc88e74f7f559df1ab09fdfeb7c228f0dfce84ef863555812222a943e25R1469

and since the otel components use this functionality it needs to be up to date with 1.35.0.

Copy link
Member

Choose a reason for hiding this comment

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

sorry, that link doesn't point me to anywhere. I just meant that there's no grpc upgrade in go.mod in this PR.

Copy link
Member Author

Choose a reason for hiding this comment

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

the grpc upgrade is actually due to the otel upgrade. was trying to link to the go.sum changes under ./cmd/opentelemetry, but it does not appear to work.

0.20.0 otel collector requires grpc 1.35.0. since the components under ./cmd/opentelemetry reference Jaeger core, it also has to be up to date with 1.35.0 even though it is not explicitly using it in its own go.mod.

Copy link
Member

Choose a reason for hiding this comment

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

I see. Have you tried bumping grpc to the same ver in the main go.mod? I just tried it and it seems to work, and I think it's better to keep the two in sync

$ go get google.golang.org/[email protected]
go: downloading google.golang.org/grpc v1.35.0
go: downloading google.golang.org/genproto v0.0.0-20200526211855-cb27e3aa2013

$ make build-collector
(no errors)

Copy link
Contributor

Choose a reason for hiding this comment

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

Have you tried bumping grpc to the same ver in the main go.mod?

Isn't this what dependabot did in another PR?

Copy link
Member Author

Choose a reason for hiding this comment

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

google.golang.org/grpc is currently at 1.29.1.

attempting an upgrade now to 1.35.0, but getting some failed tests. i will see if i can't iron these out today.

Copy link
Contributor

Choose a reason for hiding this comment

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

Might be worth checking this: #2771

@mergify mergify bot dismissed yurishkuro’s stale review February 11, 2021 13:24

Pull request has been modified.

@yurishkuro
Copy link
Member

@joe-elliott should we close this?

@joe-elliott
Copy link
Member Author

Yup, I think this no longer makes sense.

@jpkrohling jpkrohling added this to the Release 1.23.0 milestone Jun 4, 2021
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.

3 participants