Separate TSO into an independent service

[rleungx]

Development Task

[binshi-bing]

assign to me?

[rleungx]

assign to me?

Yes, but I cannot find you on the assignee list previously. lol

[binshi-bing]

To separate TSO into an independent service #5836, we define a new TSO service in protobuf to wraps up all the TSO related rpcs, then we can start a gPRC server which provides TSO service only.

Separate TSO into an independent service (Deadline: 02/20/2023)

Pre-work tracked below

• *: Introduce the service registry #5779 @nolouch
• config: remove config dependency for tso #5771 @rleungx
• (Cancelled) Support tso service #1038 in kvproto repo @rleungx
• (Cancelled) *: support tso gRPC interfaces #5852 @rleungx
• Provide API service interfaces #5849 @rleungx
  • storage: add TSO storage #5874

Deployment Tasks @binshi-bing @lhy1024 @rleungx

• Make the service start with independent mode #5837 (Deadline: 02/20/2023) @lhy1024
  • cmd
    • *: add service subcommand #5971 @rleungx
    • Refactor cobra command entrypoint #5998 @binshi-bing (hold)
  • refactor
    • server: decouple start of etcd client from server #5857 @lhy1024
    • *: refactor server entry point to support multi-mode service #5921 @binshi-bing
    • server: move client function to util #5964 @lhy1024
  • decouple dependency @lhy1024
    • scheduler: move init function #5956 @lhy1024
      • scheduler: move init function #5934 @lhy1024
      • *: refactor scheduler test and move scheduler register #5957 @lhy1024
    • *: decouple the dependency between server and mcs #5933 @lhy1024
  • service mode server
    • resource_manager: add service mode server #5994 @lhy1024
    • resource_manager: make test stable #6047 @lhy1024
• Add an independent TSO grpc service (Deadline: 02/15/2023) @binshi-bing, @lhy1024, @rleungx
  • (pr in review) Define an independent (Tenant) TSO gRPC server kvproto/pull/1053 @binshi-bing
  • basic implement tso gPRC service #5949 @binshi-bing
    • split from 5949 -- Refactor some common utilities which will be used by the upcoming TSO microservice change #5985
    • split from 5949 -- Implement tso grpc service include both server side and client side in a basic manner #5986
  • Initialize/start tso service @binshi-bing
    • config: refactor TSO config #5902 @rleungx
    • Add skeleton to initialize tso microservice #5917
    • Clean config, log initialization and refactor version info #6007
    • split from 5949 -- Init TSO service and start service loop  #6008
  • Implement TSO Client and provide general client side service discovery framework and general gPRC stream handling framework. #6037 @binshi-bing
  • Improve PD/TSO-MCS Service Discovery and TSO Client. #6090 @binshi-bing
• etcd storage interface related (Deadline: 02/15/2023) @rleungx
  • pkg: support service discovery #5911 @rleungx
  • Support tso microservice auto service discovery in the pd client. #6065 @binshi-bing
  • etcdutil: add dial keep alive params to switch connect as soon as possible #6059 @lhy1024
  • etcdutil: support multi backends client #6046 @lhy1024
  • tso: migrate tso key to new one #5942 @rleungx (hold)
• tests and bootstrapping (Deadline: 02/20/2023, in parallel with milestone 2 (sharded tenant tso)) @rleungx @lhy1024 @binshi-bing
  • integration test
  • add bootstrap process

Describe alternatives you've considered

Without defining a new TSO service in protobuf, the TSO microservice needs to be provided by the original all-in-one PD gPRC server which also registers all other services and initializes all configurations and many other things unnecessarily. It will be harder to decouple TSO service/module from other services/modules and to evolve to an independent Tenant TSO service.

Teachability, Documentation, Adoption, Migration Strategy

[binshi-bing]

@rleungx could you grant me the write permission to this issue?

[binshi-bing]

Define an independent TSO gRPC server pingcap/kvproto#1053