Skip to content

Commit

Permalink
cherry pick pingcap#2753 to release-3.1
Browse files Browse the repository at this point in the history
Signed-off-by: ti-srebot <[email protected]>
  • Loading branch information
tiancaiamao authored and ti-srebot committed Jul 10, 2020
1 parent 63c05a2 commit 2e2e3cb
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions faq/tidb-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,16 @@ Yes, it is. When all the required services are started, you can use TiDB as easi

Currently, TiDB supports the majority of MySQL 5.7 syntax, but does not support trigger, stored procedures, user-defined functions, and foreign keys. For more details, see [Compatibility with MySQL](/mysql-compatibility.md).

If you use the MySQL 8.0 client and it fails to connect to TiDB, try to add the `default-auth` and `default-character-set` options:

{{< copyable "shell-regular" >}}

```shell
mysql -h 127.0.0.1 -u root -P 4000 --default-auth=mysql_native_password --default-character-set=utf8
```

This problem occurs because MySQL 8.0 changes the [authentication plugin](/security-compatibility-with-mysql.md) default in MySQL 5.7. To solve this problem, you need to add the options above to specify using the old encryption method.

#### How is TiDB highly available?

TiDB is self-healing. All of the three components, TiDB, TiKV and PD, can tolerate failures of some of their instances. With its strong consistency guarantee, whether it’s data machine failures or even downtime of an entire data center, your data can be recovered automatically. For more information, see [TiDB architecture](/architecture.md).
Expand Down

0 comments on commit 2e2e3cb

Please sign in to comment.