Releases Notes and Announcements

Release Notes

Product Introduction

Overview

Strengths

Use Cases

Purchase Guide

Billing Overview

Billing Mode

Refund

Configuration Adjustments

Getting Started

Preparations

Creating a Private Cluster

Creating a SQL Job

Creating a JAR Job

Creating an ETL Job

Creating a Python Job

Operation Guide

Managing Jobs

Developing Jobs

Monitoring Jobs

Job Logs

Events and Diagnosis

Managing Metadata

Managing Checkpoints

Tuning Jobs

Managing Dependencies

Managing Clusters

Managing Permissions

SQL Developer Guide

Overview

Glossary and Data Types

DDL Statements

DML Statements

Merging MySQL CDC Sources

Connectors

SET Statement

Operators and Built-in Functions

Identifiers and Reserved Words

Python Developer Guide

ETL Developer Guide

Overview

Glossary

Connectors

FAQ

Abnormal TaskManager Pod Exit

PDF

포커스 모드

폰트 크기

마지막 업데이트 시간: 2023-11-07 16:57:54

Overview
TaskManagers of a Flink Job run in a Kubernetes Pod. When the Pod stops, the Pod exit event is generated, and you can determine whether the Pod is in exception based on the return code, status, and other information.
Note
 The same Pod may be re-built several times by Kubernetes due to exceptions, so you may receive an identical event several times.
Trigger conditions
The system monitors the exit of the TaskManager Pod in real time, and determines whether an exit is caused by SIGTERM based on the exit code (the normal exit code is 143). An exit code other than 143 indicates that the exit is not initiated by the JobManager, but is caused by TaskManager errors, and this case is determined as an abnormal Pod exit event.
Alarm configuration
You can configure an alarm policy as instructed in Configuring Event Alarms (Events) for this event to receive trigger and clearing notifications in real time.
Suggestions
Status Code
Possible Cause
Solution
137
The memory occupied by the job exceeded the memory quota of the Pod, and the Pod was killed due to OOM.
Increase the operator parallelism and the Task Manager spec (CUs) as instructed in Configuring Job Resources.
-1
This is the code of the basic policy, indicating that the Pod has exited, but no exit code is returned due to system errors or other reasons.
Submit a ticket to contact the technicians for help.
0
During the startup process, the Pod cannot assign IPs in the associated subnet (no IPs available, for example), resulting in startup failure and exit.
Check whether available IPs are sufficient in the VPC subnet associated with the cluster. If yes, submit a ticket to contact the technicians for help.
1
An exception occurred during Flink initialization, resulting in startup failure.
This is generally caused by basic conflicts or overwriting of critical configuration files. You can search logs by Could not start cluster entrypoint and view relevant exceptions.
If no cause can be identified, submit a ticket to contact the technicians for help.
2
A fatal error occurred during the startup of the Flink JobManager.
Search logs by Fatal error occurred in the cluster entrypoint and view relevant exceptions.
If no cause can be identified, submit a ticket to contact the technicians for help.
239
An uncaptured fatal error occurred in Flink execution threads.
Search logs by produced an uncaught exception. Stopping the process and other keywords and view relevant exceptions.
If no cause can be identified, submit a ticket to contact the technicians for help.
﻿

도움말 및 지원

문제 해결에 도움이 되었나요?

더 자세한 내용은 문의하기 또는 티겟 제출 을 통해 문의할 수 있습니다.

피드백

tencent cloud

Stream Compute Service

Abnormal TaskManager Pod Exit

Overview

Trigger conditions

Alarm configuration

Suggestions

도움말 및 지원

Status Code	Possible Cause	Solution
137	The memory occupied by the job exceeded the memory quota of the Pod, and the Pod was killed due to OOM.	Increase the operator parallelism and the Task Manager spec (CUs) as instructed in Configuring Job Resources.
-1	This is the code of the basic policy, indicating that the Pod has exited, but no exit code is returned due to system errors or other reasons.	Submit a ticket to contact the technicians for help.
0	During the startup process, the Pod cannot assign IPs in the associated subnet (no IPs available, for example), resulting in startup failure and exit.	Check whether available IPs are sufficient in the VPC subnet associated with the cluster. If yes, submit a ticket to contact the technicians for help.
1	An exception occurred during Flink initialization, resulting in startup failure.	This is generally caused by basic conflicts or overwriting of critical configuration files. You can search logs by `Could not start cluster entrypoint` and view relevant exceptions. If no cause can be identified, submit a ticket to contact the technicians for help.
2	A fatal error occurred during the startup of the Flink JobManager.	Search logs by `Fatal error occurred in the cluster entrypoint` and view relevant exceptions. If no cause can be identified, submit a ticket to contact the technicians for help.
239	An uncaptured fatal error occurred in Flink execution threads.	Search logs by `produced an uncaught exception. Stopping the process` and other keywords and view relevant exceptions. If no cause can be identified, submit a ticket to contact the technicians for help.