/tmp/tidb was not automatically created

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

Original topic: tmp/tidb没有自动创建

| username: 胡杨树旁

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Enter TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]
An error occurred when creating an index on a table with 1 billion rows.


It was found that the tmp/tidb/tmp_ddl-4001 directory was not automatically created. Manually creating it temporarily resolved the issue. I would like to ask what caused the directory not to be automatically created during deployment and where should I start troubleshooting?

| username: 啦啦啦啦啦 | Original post link

Was it upgraded in place from a lower version?

| username: 胡杨树旁 | Original post link

Upgraded to version 7.0.0, it shouldn’t be considered a low version.

| username: 啦啦啦啦啦 | Original post link

It seems that this issue only started from version 7.1. Upgrading from versions prior to 7.1 will encounter this problem.

| username: 胡杨树旁 | Original post link

I saw in the official documentation that it was introduced starting from version 6.3.

| username: 有猫万事足 | Original post link

This bug was blocked when the corresponding PR was merged into the 7.1 branch… so it wasn’t fixed in 7.1.1.

Now, as of July 19th, it has been merged into the master branch.
It has been fixed, but not completely fixed. :joy:

| username: zhanggame1 | Original post link

It still hasn’t been fixed.

| username: 胡杨树旁 | Original post link

I don’t know in which version this will be fixed.

| username: 有猫万事足 | Original post link

The fix for this issue was only merged into the master branch and it was after the release of version 7.2.
This means that version 7.2 also doesn’t have the fix, so we’ll have to wait for version 7.3.
The PR for the 7.1 branch is blocked, so if this issue isn’t resolved before the release of the next version 7.1.2, version 7.1.2 will still not have this bug fixed.

| username: redgame | Original post link

Manually build one…

| username: ShawnYan | Original post link

There is also an issue corresponding to this, and it is still open.

| username: TiDBer_iCdTOZ1r | Original post link

This issue should only occur in the new version.

| username: cy6301567 | Original post link

Don’t upgrade to the latest version all at once; using version 6.x is relatively more stable.

| username: ShawnYan | Original post link

Some team members have already upgraded to 7.1.1 in the production environment. Also, the workaround is very important.

| username: system | Original post link

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