You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "AlexHu (Jira)" <ji...@apache.org> on 2022/11/30 06:52:00 UTC

[jira] [Commented] (FLINK-30244) When task using udf/udtf with jni, on k8s session the old TM will shut down and create new TM or the task will fail

    [ https://issues.apache.org/jira/browse/FLINK-30244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641092#comment-17641092 ] 

AlexHu commented on FLINK-30244:
--------------------------------

Sorry, now I have given more details about my problem. 

> When task using udf/udtf with jni, on k8s session the old TM will shut down and create new TM or the task will fail
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30244
>                 URL: https://issues.apache.org/jira/browse/FLINK-30244
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.15.3
>            Reporter: AlexHu
>            Priority: Major
>         Attachments: image-2022-11-30-14-47-50-923.png
>
>
> We face a problem when we try to use flink on k8s to execute task with udf/udtf. When we finished or canceled a job and submit a same job, the old TM will be not reachable and restart. Why the TM have to be restart? In session mode, the TM should be reused by JM. Moreover, if we off restart strategy, this task will fail.
> !image-2022-11-30-14-47-50-923.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)