clarax opened a new pull request, #25242:
URL: https://github.com/apache/flink/pull/25242
## What is the purpose of the change
Scheduled maintenance or buggy nodes on Kubernetes can result random pod
termination and eventually a series of job restarts due to rolling restart of
the Kubernetes cluster nodes. The larger the job is the higher the chance it is
affected. The jobs should be able to auto-recover from these issues, but can
cause unwanted turbulence in large scale pipeline.
In this case, it is very difficult to identify what is causing the restarts
without knowing the issue at Kubernetes layer and the keyword to search with
because it is logged at INFO level.
We need to log this at higher level. If changing it from INFO to ERROR
breaks monitoring we should at least log as warning.
## Brief change log
- Change the log level from INFO to WARN
## Verifying this change
This change added tests and can be verified as follows:
- *Manually verified the change at local
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? No
- If yes, how is the feature documented? not applicable
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
