You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/01/29 03:48:00 UTC
[GitHub] [airflow] getElementsByName opened a new issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
getElementsByName opened a new issue #13967:
URL: https://github.com/apache/airflow/issues/13967
<!--
Welcome to Apache Airflow! For a smooth issue process, try to answer the following questions.
Don't worry if they're not all applicable; just try to include what you can :-)
If you need to include code snippets or logs, please put them in fenced code
blocks. If they're super-long, please use the details tag like
<details><summary>super-long log</summary> lots of stuff </details>
Please delete these comment blocks before submitting the issue.
-->
<!--
IMPORTANT!!!
PLEASE CHECK "SIMILAR TO X EXISTING ISSUES" OPTION IF VISIBLE
NEXT TO "SUBMIT NEW ISSUE" BUTTON!!!
PLEASE CHECK IF THIS ISSUE HAS BEEN REPORTED PREVIOUSLY USING SEARCH!!!
Please complete the next sections or the issue will be closed.
These questions are the first thing we need to know to understand the context.
-->
**Apache Airflow version**: 2.0.0
**Kubernetes version (if you are using kubernetes)** (use `kubectl version`): Client v1.14.8 / Server v1.15.10
**Environment**:
- **Cloud provider or hardware configuration**: on-premise
- **OS** (e.g. from /etc/os-release): Ubuntu 18.04.5 LTS
- **Kernel** (e.g. `uname -a`): Linux 5.4.0-62-generic
- **Install tools**:
- **Others**:
**What happened**:
<!-- (please include exact error messages if you can) -->
- operator code (with xcom)
```
write_xcom = KubernetesPodOperator(
do_xcom_push=True,
...
)
```
- airflow log
- pending
```
[2021-01-29 12:32:19,604] {pod_launcher.py:269} INFO - Running command... kill -s SIGINT 1
```
#### pod
- k8s container state of `airflow-xcom-sidecar`
```
State: Terminated
Reason: Error
Exit Code: 137
```
- processes in `airflow-xcom-sidecar`
```
/airflow/xcom # ps
PID USER TIME COMMAND
1 root 0:00 /pause
6 root 0:00 sh -c sleep 9999;mkdir -p /airflow/xcom/;echo '[1,2,3,4]' > /airflow/xcom/return.json
11 root 0:00 sleep 9999
12 root 0:00 sh -c trap "exit 0" INT; while true; do sleep 30; done;
23 root 0:00 sh
31 root 0:00 sleep 30
48 root 0:00 ps
```
**What you expected to happen**:
<!-- What do you think went wrong? -->
- send the INT signal to the sidecar's main process (It is PID 12 in the previous example)
**How to reproduce it**:
<!---
As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
If you are using kubernetes, please attempt to recreate the issue using minikube or kind.
## Install minikube/kind
- Minikube https://minikube.sigs.k8s.io/docs/start/
- Kind https://kind.sigs.k8s.io/docs/user/quick-start/
If this is a UI bug, please provide a screenshot of the bug or a link to a youtube video of the bug in action
You can include images using the .md style of
To record a screencast, mac users can use QuickTime and then create an unlisted youtube video with the resulting .mov file.
--->
- It is probably related to setting up k8s about container runtime.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-770249804
I honestly do not understand what is the problem and expectations here. Could you please elaborate on what you were trying to achive and what did not work?
Please be as descriptive as possible.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] getElementsByName commented on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
getElementsByName commented on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-776559355
@potiuk
### Problem
- (airflow) The `airflow-xcom-sidecar` container waits a SIGINT signal by `trap "exit 0" INT;`.
- (airflow) The pod launcher in the airflow package stops the sidecar's main processor by `kill -s SIGINT 1`
- (k8s) The PID1 process can be a init process made by a container runtime like the docker.
- In the top example. The sidecar's main process is not PID 1.
- In the top example, the command (`kill -s SIGINT 1`) makes the 137 exit code.
### Expectation
- The pod launcher can send the SIGINT signal to the sidecar's main process other than PID 1 .
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] github-actions[bot] closed issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
github-actions[bot] closed issue #13967:
URL: https://github.com/apache/airflow/issues/13967
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] ashb commented on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
ashb commented on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-777758814
This is indeed caused by `shareProcessNamespace`. Why/how are you setting that?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] boring-cyborg[bot] commented on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-769555601
Thanks for opening your first issue here! Be sure to follow the issue template!
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] github-actions[bot] commented on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-812945464
This issue has been automatically marked as stale because it has been open for 15 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] github-actions[bot] commented on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-817220905
This issue has been closed because it has not received response from the issue author.
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] getElementsByName edited a comment on issue #13967: KubernetesPodOperator with do_xcom_push makes 137 exit code error
Posted by GitBox <gi...@apache.org>.
getElementsByName edited a comment on issue #13967:
URL: https://github.com/apache/airflow/issues/13967#issuecomment-776559355
@potiuk
### Problem
- (airflow) The `airflow-xcom-sidecar` container waits a SIGINT signal by `trap "exit 0" INT;`.
- (airflow) The pod launcher in the airflow package stops the sidecar's main processor by `kill -s SIGINT 1`
- (k8s) The PID1 process can be a init process made by a container runtime like the docker.
- In the top example. The sidecar's main process is not PID 1.
- In the top example, the command (`kill -s SIGINT 1`) makes the 137 exit code.
### Expectation
- The pod launcher can send the SIGINT signal to the sidecar's main process other than PID 1 only.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org