Encountering WARN logs when setting up TiDB v6.5.5

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

Original topic: 搭建tidb v6.5.5日志出现warn

| username: 答辩潮人

[TiDB Usage Environment] Production Environment
[TiDB Version] v6.5.5
[Reproduction Path]

  1. tiup cluster check ./topology.yaml
  2. tiup cluster deploy test-1 v6.5.5 ./topology.yaml
  3. tiup cluster start test-1 --init
    [Encountered Problem: Phenomenon and Impact]

{“level”:“warn”,“ts”:“2023-10-18T18:38:14.906+0800”,“logger”:“etcd-client”,“caller”:“v3@v3.5.7/retry_interceptor.go:62”,“msg”:“retrying of unary invoker failed”,“target”:“etcd-endpoints://0xc0006ee1c0/”,“attempt”:0,“error”:“rpc error: code = DeadlineExceeded desc = context deadline exceeded”}

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

| username: 答辩潮人 | Original post link

This error occurred after completing the command tiup cluster start test-1 --init, and the log level is warn. The cluster has been set up, but I’m worried about other potential impacts.

| username: Billmay表妹 | Original post link

Timezone setting issue? The following error message indicates that the deadline has been exceeded?

| username: 答辩潮人 | Original post link

There is no problem with the time zone, both are CST, and the time matches.

| username: zhanggame1 | Original post link

Is the cluster status normal when displayed?

| username: 像风一样的男子 | Original post link

If you can’t stand it, just handle it.
Edit the /etc/fstab file and add the nodelalloc and noatime configurations as shown below:

| username: yiduoyunQ | Original post link

The logs in tidb_stderr.log?

| username: tidb菜鸟一只 | Original post link

If it’s not an error, you don’t need to worry about it.

| username: 随缘天空 | Original post link

Warnings generally do not affect it. This warning is mainly caused by not setting parameters in /etc/fstab when you mounted the disk.

| username: 答辩潮人 | Original post link

The error here is related to the disk environment and does not have an impact. However, the error with etcd-client is problematic.

| username: 答辩潮人 | Original post link

It’s not an error log.

| username: 答辩潮人 | Original post link

But it shouldn’t affect this.

| username: 答辩潮人 | Original post link

Normal, no issues. However, when performing scaling up or scaling down, there will be errors in the text part.

| username: TiDBer_小阿飞 | Original post link

The warn status shouldn’t have much impact, right?

| username: 随缘天空 | Original post link

Well, it’s best to configure it in the system parameters.

| username: Jolyne | Original post link

You can ignore the warnings. Use the display command to check the cluster status. If everything is normal, there’s no issue. If there are any nodes in a down state, you can check the logs of the down nodes individually.

| username: Soysauce520 | Original post link

Errors that can be ignored

| username: 答辩潮人 | Original post link

It has now affected the operation of tiup cluster reload xxx -N xxxx:9090.

  "code": 1,
  "error": "context deadline exceeded",
  "errorVerbose": "context deadline exceeded\n

| username: Jolyne | Original post link

This looks like INFO, not an error. So, was your reload successful or not?

| username: 答辩潮人 | Original post link

Execution was not successful.