TiDB logs show "Unable to get collation ID by name, use ID of the default collation instead," is this an issue?

Translated
1

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

Original topic: tidb日志有Unable to get collation ID by name, use ID of the default collation instead，是问题嘛

| username: wluckdog

[TiDB Environment] Unable to get collation ID by name, use ID of the default collation instead
[TiDB Version] v6.5.0
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]

image
image1832×816 195 KB

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: hey-hoho | Original post link

You used a collation that is not supported by TiDB, so it replaced it with the default value utf8mb4_bin. Please evaluate whether this has any impact on the application side.

3
| username: db_user | Original post link

What is your collation configuration? Did you configure the collation supported by the cluster, or did you not set the new collation parameter to true?

4
| username: liusf1993 | Original post link

Hello, I have the same issue with many identical logs. I checked the table’s COLLATION, and they are ‘utf8_bin’ and ‘utf8mb4_bin’, which are in the list of collations supported by TiDB. What other adjustments can be made to eliminate this warning message?
My version is v5.0.6.

5
| username: db_user | Original post link

What is the collation id of your alert? Could you please provide it? Also, could you kindly send two complete alerts?

6
| username: liusf1993 | Original post link

Not sure where the collation name is empty, all database tables are specified as utf8_bin and utf8mb4_bin.
[2023/02/27 11:01:10.054 +08:00] [WARN] [expr_to_pb.go:179] [“Unable to get collation ID by name, use ID of the default collation instead”] [name=] [“default collation ID”=46] [“default collation”=utf8mb4_bin]
[2023/02/27 11:01:10.054 +08:00] [WARN] [expr_to_pb.go:179] [“Unable to get collation ID by name, use ID of the default collation instead”] [name=] [“default collation ID”=46] [“default collation”=utf8mb4_bin]

7
| username: db_user | Original post link

It looks like a bug.
Coprocessor will get invalid collation ID from TiDB · Issue #29697 · pingcap/tidb (github.com)

Have you enabled the new sorting rule parameter and set it to True?

8
| username: wluckdog | Original post link

No new collation was opened, system default parameters.

9
| username: db_user | Original post link 
select * from mysql.tidb where variable_name like '%new_collation_enabled%';

Check if the result is false. If it is false, then it should be that bug. However, it’s strange because your version is so new, and that issue seems to have already been merged.

10
| username: system | Original post link

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