TiDB Log Error [ERROR] [error.go:291] ["encountered error"] [error="[pd] store field in rpc response not set"]

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

Original topic: tidb 日志报错 [ERROR] [error.go:291] [“encountered error”] [error=“[pd] store field in rpc response not set”]

| username: foxchan

【TiDB Usage Environment】Production Environment
【TiDB Version】
【Reproduction Path】Removed one PD node, added a new PD node, and up to now, TiDB has not been restarted.
【Encountered Problem: Symptoms and Impact】
TiDB started logging this message, is it affecting anything?

[2024/04/18 17:59:14.527 +08:00] [ERROR] [error.go:291] [“encountered error”] [error=“[pd] store field in rpc response not set”] [stack=“github.com/tikv/client-go/v2/error.Log\n\t/go/pkg/mod/github.com/tikv/client-go/v2@v2.0.1-0.20230704072904-34f99fa358b6/error/error.go:291\ngithub.com/tikv/client-go/v2/internal/locate.(*RegionCache).checkAndResolve\n\t/go/pkg/mod/github.com/tikv/client-go/v2@v2.0.1-0.20230704072904-34f99fa358b6/internal/locate/region_cache.go:475\ngithub.com/tikv/client-go/v2/internal/locate.(*RegionCache).asyncCheckAndResolveLoop\n\t/go/pkg/mod/github.com/tikv/client-go/v2@v2.0.1-0.20230704072904-34f99fa358b6/internal/locate/region_cache.go:443”]

| username: TiDBer_jYQINSnf | Original post link

Execute pd-ctl store to see if everything is normal.

| username: TiDBer_JUi6UvZm | Original post link

Bumping this up.

| username: zhaokede | Original post link

There is an issue with the ERROR level log.
Is this PD connected?

| username: wangkk2024 | Original post link

Bump.

| username: xfworld | Original post link

Does this error persist continuously? Or does it only appear when switching PD, and then it disappears?

| username: foxchan | Original post link

It appears regularly, every minute. It’s still happening now.

| username: xfworld | Original post link

Check the various parameters through Grafana.

How many TiDB nodes are there? Is each node experiencing this error?

| username: foxchan | Original post link

Directly upgrade to 7.5.1, the issue is resolved.

| username: xfworld | Original post link

Okay, it seems to be a known bug.

| username: 舞动梦灵 | Original post link

I’m not quite sure, it might be a bug in recognizing parameters. After upgrading, all default values for unset parameters will be reset.