Re: [VOTE] TiKV Graduation
toggle quoted messageShow quoted text
Thanks TOC for raising this concern. I am Tang Liu, and I am speaking here both as a TiKV maintainer and a member of the broader eco-system & community.
It’s true that Placement Driver is an indispensable part for TiKV, as the meta store and central scheduling center.
The original rationale behind the current placement of PD (under PingCAP with TiDB, the distributed SQL database) is to take PD as a significant dependency library in the TiDB eco-system (TiKV included) and other TiKV-alike stores as well.
Besides TiKV, there are multiple major TiDB features or components that depend on PD. For example, Dashboard (https://docs.pingcap.com/tidb/dev/dashboard-intro), our visual diagnosis platform, depends on PD to obtain necessary data. Unistore (https://github.com/ngaut/unistore), a KV store in GO to quickly validate TiDB optimizations depends on PD to deploy and run. Some scenario based features like multi-data center are made possible by PD. Outside of TiDB, there are other projects building distributed KV stores based on PD.
With a vibrant TiDB ecosystem of almost 1000 adopters and other PD based projects, we believe PD has been in a health and sustained maintenance and has formed its own eco-system over time.
However, if this could not clear the concern of TOC, we are willing to migrate the entire PD library to the TiKV project.
Frederick Kautz <frederick@...> 于2020年8月11日周二 上午4:51写道：