Upgrading to version V6.1.5, numerous errors reported on the Failed Query OPM panel

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

Original topic: 升级V6.1.5版本,Failed Query OPM面板大量报错

| username: wwb519

[TiDB Usage Environment] Production Environment / Testing / PoC
Production Environment
[TiDB Version]
[Reproduction Path] Operations performed that led to the issue
Upgraded from V4.0.15 to V6.1.5
[Encountered Issue: Issue Phenomenon and Impact]

No information about this error code was found in the tidb log, and the tidb cluster is operating normally.

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

| username: weixiaobing | Original post link

There should be some set variable error. You can search the logs for the keyword “variable”.

| username: wwb519 | Original post link

No logs recorded.

| username: wwb519 | Original post link

The image you provided is not visible. Please provide the text you need translated.

| username: weixiaobing | Original post link

This keyword variable

| username: weixiaobing | Original post link

In the TiDB server panel, it should indicate which machine this error is on. You can check it.

| username: wwb519 | Original post link

The keyword “variable” was also searched, but there are no records.

| username: wwb519 | Original post link

I have already searched the logs of these two TiDB instances, but there are no records.

| username: weixiaobing | Original post link

Search for the keyword “command dispatched failed”.

| username: wwb519 | Original post link

The latest search record is from May 6th, and there have been no new records since then.

| username: TiDBer_UUTlqVvZ | Original post link

error = ‘’’
function %s has only noop implementation in tidb now, use tidb_enable_noop_functions to enable these functions

variable:1235 is related to function implementation. The “noop implementation” mentioned in the error message refers to a special function implemented in TiDB that does not perform any operations and simply returns an empty result set. These functions are usually for compatibility purposes, allowing MySQL code to run in TiDB without errors.

If you encounter this error, you can try using the tidb_enable_noop_functions variable to enable these functions. This variable was introduced in TiDB v4.0.0 to control the behavior of noop functions. By default, TiDB returns an error when you attempt to use an unimplemented feature. When the variable is set to ON, TiDB will silently ignore these unavailable features, which is useful when you cannot change the SQL code.

Here is an example of how to use the tidb_enable_noop_functions variable:

set @@tidb_enable_noop_functions=1;  -- session level
set @@global.tidb_enable_noop_functions=1;  -- global level, note that it takes effect in new sessions

Please note that enabling noop functions may cause unexpected behavior in your application, as it allows TiDB to ignore certain syntax without providing errors. Therefore, the default value OFF is considered safe.

Hope this helps you resolve the issue!

Related documentation: 系统变量 | PingCAP 归档文档站

| username: TiDBer_pkQ5q1l0 | Original post link

I have this error.