Cody (Xuecheng) Zhang
Cody (Xuecheng) Zhang
/run-all-tests
/run-pull-e2e-kind-br
/run-pull-e2e-kind-tikv-scale-simultaneously
cloud you use TiCDC? ref https://docs.pingcap.com/tidb/stable/ticdc-overview Otherwise, you may try the reverse operation as https://docs.pingcap.com/tidb-in-kubernetes/stable/migrate-tidb-to-kubernetes - create a TiDB Cluster on physical machines to join the cluster - scale in...
As TiDB Operator can spawn a simple TiKV cluster, but we don't fully test this, and this is not the goal of TiDB Operator.
TiDB Operator relies on an internal component named "discovery" to dynamically bootstrap the PD cluster. https://github.com/pingcap/tidb-operator/tree/master/cmd/discovery and the `join` file is generated by PD, ref https://github.com/tikv/pd/blob/2c07c241114fe9afabd9927ecbee61c4252f2d8e/server/join/join.go#L93
> It seems like pd itself reads the `join` file to do corresponding operations, why would the start script read it and add the `--join` args? PD wouldn't read the...
> https://github.com/pingcap/tidb-operator/blob/master/pkg/discovery/discovery.go#L271 need to be fixed and include not only `PeerMembers` but `Members` as well. `Members` should already be included in `returnPDMembers := []string{pdURL}` where `pdURL` is the URL to...
> > Members should already be included in returnPDMembers := []string{pdURL} where pdURL is the URL to the local Service. > > For example, we are running tidb in 3...
> > Can you show the case with the wrong PD URL? Yeah, connecting and fetching members may be better. > > For example we have a heterogeneous tidb cluster...