What are the issues with oversized TiKV regions?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tikv region 过大有什么问题

| username: Raymond

May I ask, if a TiKV region becomes too large and does not split in time, what negative impacts might it have?

| username: TiDBer_jYQINSnf | Original post link

Regions that are too large are prone to hotspots, and migrating regions is slow. Other than that, there are no major issues.

| username: xfworld | Original post link

Unless manually adjusted, it will generally split automatically and promptly.

Otherwise, it will greatly affect the network bandwidth…

| username: tidb菜鸟一只 | Original post link

To the extreme, if you have a table that is 20G and a region that is also 20G, having multiple TiKV nodes is useless. You still have to query the leader region for data, and you also have to store several follower regions on other nodes at the same time. Can this still be called a distributed database…