Re: [PR] [FLINK-31234][kubernetes] Add an option to redirect stdout to log dir. [flink]

Sat, 12 Oct 2024 01:02:59 -0700 


huwh commented on PR #22138:
URL: https://github.com/apache/flink/pull/22138#issuecomment-2408448977

   > @huwh 感谢回复，环境如下： flink-kubernetes-operator 1.9.0 flink: 
flink:1.18.1-scala_2.12 log4j-console.properties 是镜像默认的
   > 
   > ```yaml
   > apiVersion: flink.apache.org/v1beta1
   > kind: FlinkDeployment
   > metadata:
   >   name: basic
   > spec:
   >   image: flink:1.18.1-scala_2.12
   >   flinkVersion: v1_18
   >   ingress:
   >     className: "nginx"
   >     template: "{{name}}.fo.xyuqing.com" # 引号必须有
   >   podTemplate:
   >     spec:
   >       containers:
   >         - name: flink-main-container
   >           ports:
   >             - name: metrics
   >               containerPort: 9249
   >               protocol: TCP
   >           env:
   >             - name: TZ  # 设置容器运行的时区
   >               value: Asia/Shanghai
   >   flinkConfiguration:
   >     taskmanager.numberOfTaskSlots: "2"
   >     env.stdout-err.redirect-to-file: "true"
   >     metrics.reporter.prom.factory.class: 
org.apache.flink.metrics.prometheus.PrometheusReporterFactory
   >   serviceAccount: flink
   >   jobManager:
   >     resource:
   >       cpu: 1
   >       memory: 2G
   >   taskManager:
   >     resource:
   >       cpu: 1
   >       memory: 2G
   >   job:
   >     jarURI: local:///opt/flink/examples/streaming/StateMachineExample.jar
   >     parallelism: 2
   >     upgradeMode: stateless
   > ```
   > 
   > 
![image](https://private-user-images.githubusercontent.com/24886602/374858558-20975efa-0e45-4fc3-94c9-d8301b350d33.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg3MTYzMzMsIm5iZiI6MTcyODcxNjAzMywicGF0aCI6Ii8yNDg4NjYwMi8zNzQ4NTg1NTgtMjA5NzVlZmEtMGU0NS00ZmMzLTk0YzktZDgzMDFiMzUwZDMzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDEyVDA2NTM1M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWNhYTM1NDAyZTlkODVkMmFhYzM0MTU3MDQ2ZDI4ZTkzOWQ3NTIyODQzOWNhYzI2ZTc1NTJjZmZiYTJmNDAyNzImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.xAurRSUTvlAa0q-33R7WuSWRX2h8kD9usBFh8iJm3gE)
   > 
   > 
![image](https://private-user-images.githubusercontent.com/24886602/374857942-ce2bcf7b-94dc-4df2-aa3f-a0d6b484c2d0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg3MTYzMzMsIm5iZiI6MTcyODcxNjAzMywicGF0aCI6Ii8yNDg4NjYwMi8zNzQ4NTc5NDItY2UyYmNmN2ItOTRkYy00ZGYyLWFhM2YtYTBkNmI0ODRjMmQwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDEyVDA2NTM1M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE0MDE0ZjZmNTZmMDI4MjJmODgyMmMyNjFmOTc2N2I0M2Y3YTgxNDI3NTRmYmNhNDg1ZjAyYTViMmU3MGE1YmEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.e_jr7DAwGhCSwcc9qVlQSz5osGqKz2gplZw0VVrWQns)
   > 
   > 我的意思是虽然 `kubectl logs -f pods/xxx ` 不会打印log4j2的日志内容，但是对应的 `xxx.out` 
文件还是包含有 log4j2 `xxx.log`的日志内容，最终导致 代码中的log4j的输出会存在两份，也就会占两份存储，而且`xxx.out` 
文件不能做到按大小或时间自动切分
   
   
   This is because flink-kubernetes-operator uses its log4j-console.properties, 
which does not support the console appender filtering function.
   
   Currently, flink-kubernetes-operator does not recommend enable 
env.stdout-err.redirect-to-file, which does cause log duplication.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to