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

Deprecate tchannel #1975

Merged
merged 1 commit into from
Dec 13, 2019
Merged

Conversation

objectiser
Copy link
Contributor

Signed-off-by: Gary Brown gary@brownuk.com

Which problem is this PR solving?

Deprecating tchannel so can be removed from future release.

Short description of the changes

Added deprecation notice to agent flag and collector/all-in-one handler.

Signed-off-by: Gary Brown <gary@brownuk.com>
@codecov
Copy link

codecov bot commented Dec 13, 2019

Codecov Report

Merging #1975 into master will decrease coverage by 0.01%.
The diff coverage is 33.33%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1975      +/-   ##
==========================================
- Coverage   96.99%   96.97%   -0.02%     
==========================================
  Files         203      203              
  Lines       10062    10064       +2     
==========================================
  Hits         9760     9760              
- Misses        264      265       +1     
- Partials       38       39       +1
Impacted Files Coverage Δ
cmd/agent/app/reporter/flags.go 68.75% <33.33%> (-9.83%) ⬇️

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 071fc85...1c25763. Read the comment docs.

@objectiser objectiser added this to the Release 1.16 milestone Dec 13, 2019
@yurishkuro yurishkuro merged commit 530e1f1 into jaegertracing:master Dec 13, 2019
@pavolloffay
Copy link
Member

It might be also better to add deprecated annotation to all tchannel flags:

      --reporter.tchannel.discovery.conn-check-timeout duration   sets the timeout used when establishing new connections (default 250ms)
      --reporter.tchannel.discovery.min-peers int                 if using service discovery, the min number of connections to maintain to the backend (default 3)
      --reporter.tchannel.host-port string                        comma-separated string representing host:ports of a static list of collectors to connect to directly (e.g. when not using service discovery)
      --reporter.tchannel.report-timeout duration                 sets the timeout used when reporting spans (default 1s)

The deprecation message in reporter type is not that obvious

--reporter.type string                                      Reporter type to use e.g. grpc, tchannel[NOTE: Deprecated since 1.16] (default "grpc")

Like

      --discovery.conn-check-timeout duration                     (deprecated) see --reporter.tchannel.discovery.conn-check-timeout (default 250ms)
      --discovery.min-peers int                                   (deprecated) see --reporter.tchannel.discovery.min-peers (default 3)

@objectiser objectiser deleted the deprecatetchannel branch December 16, 2019 11:35
@objectiser
Copy link
Contributor Author

objectiser commented Dec 16, 2019

@pavolloffay Agree the other tchannel flags would be better deprecated.

However reporter.type is difficult, because we are not deprecating that parameter, only one of its values.

@KeaMedes
Copy link

could someone explain why tchannel is deprecated?

@pavolloffay
Copy link
Member

We have decided to use gRPC instead. IIRC tchannel also does not properly support load balancing (at least in k8s environment).

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.

4 participants