PD should not contain the log related to TiDB

[rleungx]

For users who only use the TiKV, it will be confused to see the following logs. And these logs will be printed every 5s.

[2020/06/08 11:12:48.899 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:12:53.900 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:12:58.901 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:03.902 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:08.902 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:13.903 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:18.904 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:23.905 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:28.906 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]
[2020/06/08 11:13:33.906 +08:00] [WARN] [forwarder.go:117] ["No TiDB is alive now"]

[Fullstop000]

Can we define some deployment 'mode' in such a scenario? For example, using FULL for pd + tidb + tikv and KV_ONLY for pd + tikv to decide whether we need to launch the tidb forwarder.

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[breezewish]

@HunDunDM Do you have some suggestions?

[rleungx]

Any suggestions for this issue now?

[unbyte]

Maybe KV-only users can use a PD distribution that does not include dashboard 😵

[breezewish]

I think this can be resolved when TiDB Dashboard is moved to ngm.