Sparkle

Results 64 comments of Sparkle

1. Show more detail error information ![image](https://user-images.githubusercontent.com/1284531/100044240-20f02a00-2e4a-11eb-843b-d5ddbac1fa1b.png) 1. show one error is enough ![image](https://user-images.githubusercontent.com/1284531/100044294-49782400-2e4a-11eb-8baa-c276c2237116.png) 1. too long error message overflow ![image](https://user-images.githubusercontent.com/1284531/100044319-5f85e480-2e4a-11eb-8c84-8e61c418f1d3.png)

> @baurine We also have other kind of timeouts, like proxy timeout. Could you confirm this behaviour? (e.g. whether increasing the proxy timeout is necessary). ok, I will check it.

Some features have broken, still fixing them.

support show audit list in the web UI: ![image](https://user-images.githubusercontent.com/1284531/111284708-5760e780-867b-11eb-91d0-ea06b94ef203.png)

current support backup the cluster periodically:

support downgrade a cluster: ![image](https://user-images.githubusercontent.com/1284531/113009801-dd684c80-91aa-11eb-8cbf-0a57b4ecd19f.png)

- The link about how to use [pd-ctl](https://docs.pingcap.com/zh/tidb/stable/pd-control#pd-control-%E4%BD%BF%E7%94%A8%E8%AF%B4%E6%98%8E) - The link about [how PD works](https://docs.pingcap.com/zh/tidb/stable/tidb-scheduling)

sorry for just seeing this issue, let me have a look.

hi @dveeden sorry for the late reply, recently I am handling a similar issue. For this case, according to the console information and code logic, it is because there is...

> @baurine I see the same error message. I deployed a minimum cluster following this: https://docs.pingcap.com/tidb-in-kubernetes/stable/get-started. > > hi @xpepermint , yep, I found the root cause, it is because...