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

Add CLI Option for gRPC Max Receive Message Size #3211

Closed
wants to merge 4 commits into from

Conversation

js8080
Copy link
Contributor

@js8080 js8080 commented Aug 16, 2021

Which problem is this PR solving?

Resolves #3210

Short description of the changes

Added a new CLI option for the gRPC Collector to override the default
max receive message size which is normally 4MB since some users of
Jaeger may want to record Spans which exceed the default max size.

Signed-off-by: Justin Stauffer justin.stauffer@gmail.com

@js8080 js8080 requested a review from a team as a code owner August 16, 2021 20:03
@js8080 js8080 requested a review from yurishkuro August 16, 2021 20:03
@codecov
Copy link

codecov bot commented Aug 16, 2021

Codecov Report

Merging #3211 (b2f98ec) into master (2a4aeb3) will increase coverage by 0.00%.
The diff coverage is 80.00%.

❗ Current head b2f98ec differs from pull request most recent head e418dff. Consider uploading reports for the commit e418dff to get more accurate results
Impacted file tree graph

@@           Coverage Diff           @@
##           master    #3211   +/-   ##
=======================================
  Coverage   95.90%   95.91%           
=======================================
  Files         242      242           
  Lines       14786    14794    +8     
=======================================
+ Hits        14181    14190    +9     
  Misses        525      525           
+ Partials       80       79    -1     
Impacted Files Coverage Δ
cmd/collector/app/options.go 100.00% <ø> (ø)
cmd/collector/app/server/grpc.go 65.00% <57.14%> (-0.72%) ⬇️
cmd/collector/app/builder_flags.go 100.00% <100.00%> (ø)
cmd/collector/app/collector.go 76.04% <100.00%> (+0.25%) ⬆️
cmd/query/app/server.go 95.58% <0.00%> (+1.47%) ⬆️

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 2a4aeb3...e418dff. Read the comment docs.

@js8080 js8080 force-pushed the master branch 3 times, most recently from 26c40f5 to 6d4cf49 Compare August 16, 2021 20:45
Added a new CLI option for the gRPC Collector to override the default
max receive message size which is normally 4MB since some users of
Jaeger may want to record Spans which exceed the default max size.

Signed-off-by: Justin Stauffer <justin@epic.com>
Changed collector.grpc-max-receive-message-length to
collector.grpc.max-receive-message-length for consistency.

Signed-off-by: Justin Stauffer <justin@epic.com>
collectorZipkinAllowedHeaders = "collector.zipkin.allowed-headers"
collectorZipkinAllowedOrigins = "collector.zipkin.allowed-origins"
collectorZipkinHTTPHostPort = "collector.zipkin.host-port"
collectorGRPCMaxReceiveMessageLength = "collector.grpc.max-receive-message-length"
Copy link
Member

Choose a reason for hiding this comment

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

given that we already have a grouping collector.grpc-server, I think a better name would be

collector.grpc-server.max-message-size

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will do that.

@Ashmita152
Copy link
Contributor

You would need to raise the PR from another branch of your fork (other than master) to fix these CI failures.

@js8080
Copy link
Contributor Author

js8080 commented Aug 17, 2021

You would need to raise the PR from another branch of your fork (other than master) to fix these CI failures.

Oh, shoot... I didn't realize that. Should I just delete this whole PR and then re-do it?

js8080 and others added 2 commits August 17, 2021 08:20
Changes new option from `collector.grpc.max-receive-message-length` to
`collector.grpc-server.max-message-size` as suggested during review.

Signed-off-by: Justin Stauffer <justin@epic.com>
@js8080
Copy link
Contributor Author

js8080 commented Aug 17, 2021

You would need to raise the PR from another branch of your fork (other than master) to fix these CI failures.

Oh, shoot... I didn't realize that. Should I just delete this whole PR and then re-do it?

I made a new PR in #3214 from a branch on my fork instead of from master. Closing this PR.

@js8080 js8080 closed this Aug 17, 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.

gRPC Collector Does Not Support Configurable Max Message Size
3 participants