[Bug] When k8S is deployed, only one POD can be stored in the log volume

[CCCYounger]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

我采用的是k8s部署（华为云cce），多个pod挂载同一个日志卷，发现存的文件没有区分是哪一个pod保存的，只能区分master、worker、api、alert，不能具体到哪一个worker，进一步检查后，发现每一小时的日志文件都是某一个pod的日志。
这样会导致pod重启后无法查询日志，挂载日志卷就没有意义了。

I used K8S deployment (Huawei cloud CCE), and multiple pods mounted the same log volume. I found that the saved files did not distinguish which POD saved them, but could only distinguish master, worker, API and alert, not specific worker. After further checking,It was found that the log file of each hour was the log file of a pod.
In this case, the POD cannot query logs after the restart, and it is meaningless to mount the log volume.

What you expected to happen

我查看了日志相关配置（logback-master.xml、logback-worker.xml、logback-api.xml、logback-alert.xml），配置的文件名没有区分具体的pod，这样会导致所有pod使用同一个文件。

I looked at the log configuration (logback-master. XML, logback-worker. XML, logback-api. XML, logback-alert.xml),the configured file name does not discriminate between specific pods, which results in all pods using the same file.

How to reproduce

也许文件名加入${hostname}之类的名称会更好？

Maybe the filename would be better with a name like ${hostname}?

Anything else

No response

Version

2.0.5

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

I use k8s deployment (Huawei cloud cce), multiple pods mount the same log volume, and found that the stored files do not distinguish which pod is saved, only master, worker, api, alert can not be specific. A worker, after further inspection, found that the log file for each hour was the log of a certain pod.
This will make it impossible to query the log after the pod restarts, and it will be meaningless to mount the log volume.

I used K8S deployment (Huawei cloud CCE), and multiple pods mounted the same log volume. I found that the saved files did not distinguish which POD saved them, but could only distinguish master, worker, API and alert, not specific worker. After Further checking, It was found that the log file of each hour was the log file of a pod.
In this case, the POD cannot query logs after the restart, and it is meaningless to mount the log volume.

What you expected to happen

I checked the log related configuration (logback-master.xml, logback-worker.xml, logback-api.xml, logback-alert.xml), the file name of the configuration does not distinguish the specific pod, which will cause all pods to use the same one document.

I looked at the log configuration (logback-master.XML, logback-worker.XML, logback-api.XML, logback-alert.xml), the configured file name does not discriminate between specific pods, which results in all pods using the same file.

How to reproduce

Maybe it would be better to join the filename to something like ${hostname}?

Maybe the filename would be better with a name like ${hostname}?

Anything else

No response

Version

2.0.5

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.