Inconsistent Descriptions of Region Size

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

Original topic: Region的大小存在不一致的描述

| username: Bing

Documentation Error: Please provide feedback using the template below

| username: Billmay表妹 | Original post link

The issue has been reported~ We will update you with specific progress as soon as possible~

| username: 我是咖啡哥 | Original post link

I was so scared that I quickly searched the documentation.

TiKV region-max-size modification default value from 144 MB

My understanding is that when a Region exceeds 96M, another one will be allocated, but at this time the startkey and endkey of this region are already fixed. Data within this range will continue to increase, and when it exceeds 144M, it will split.

The first description here is actually not wrong. What he wants to say is that the default size of the Region is 96M, not the split size.

| username: 我是咖啡哥 | Original post link

Simply put: greater than 96MB, a new one is allocated; greater than 144MB, one becomes two.
Default Region size region-split-size: 96MB,
Default split size region-max-size: 144MB, region-split-size / 2 * 3.

| username: Billmay表妹 | Original post link

Your understanding is correct~

The documentation is actually not wrong, but it might be a bit difficult to understand when compared,

So I have already submitted tikv: updated description about region size by hfxsd · Pull Request #12168 · pingcap/docs-cn · GitHub

The PR has been optimized to minimize the obstacles for everyone reading the documentation~

| username: Bing | Original post link

Thank you, Coffee Brother, for answering the questions.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.