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

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.

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

Pre-work tracked below

Deployment Tasks @binshi-bing @lhy1024 @rleungx

Describe alternatives you've considered

Teachability, Documentation, Adoption, Migration Strategy

Separate TSO into an independent service #5836

Description

Development Task

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions