Zakelly opened a new pull request, #23347:
URL: https://github.com/apache/flink/pull/23347
## What is the purpose of the change
The thread dump of TM is very useful to investigate the reason why
checkpoint happens to timeout. This PR make it possible for TM to print thread
dump to log when checkpoint expired.
## Brief change log
* Introduce a ```CheckpointExpiredThreadDumper``` to do the dump.
* Move a common thread dump stringifying util to
```org.apache.flink.runtime.util.JvmUtils```
* Construct an instance of ```CheckpointExpiredThreadDumper``` in
```TaskExecutor``` and pass it all the way to the ```StreamTask```
* Pass ```CheckpointFailureReason``` from ```CheckpointCoordinator``` to
```StreamTask``` via checkpoint notification when checkpoint aborted.
* When ```StreamTask``` receive the checkpoint expired notification, it will
use the ```CheckpointExpiredThreadDumper``` to print the thread dump.
## Verifying this change
This change added tests and can be verified as follows:
- Run ```CheckpointExpiredThreadDumperTest``` to verify the functionality
of ```CheckpointExpiredThreadDumper```
- Manually run a stateful test job with checkpoint timeout set to 1s
(destined to time out), check the print thread dump.
## 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)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), **Checkpointing**, Kubernetes/Yarn, ZooKeeper: (**yes** / no /
don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (**yes** / no)
- If yes, how is the feature documented? (not applicable / **docs** /
JavaDocs / not documented)
--
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]
