You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "frank wang (JIRA)" <ji...@apache.org> on 2019/03/21 10:52:00 UTC
[jira] [Commented] (FLINK-11900) Flink on Kubernetes sensitive
about arguments placement
[ https://issues.apache.org/jira/browse/FLINK-11900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797991#comment-16797991 ]
frank wang commented on FLINK-11900:
------------------------------------
{code:java}
job-cluster --job-classname <classname> --fromSavepoint <savepointPath> --allowNonRestoredState does not pick the savepoint path and does not start from it
job-cluster --fromSavepoint <savepointPath> -n --job-classname <classname> -p works for savepoint retrieval{code}
maybe you should keep them accordance, try that
> Flink on Kubernetes sensitive about arguments placement
> -------------------------------------------------------
>
> Key: FLINK-11900
> URL: https://issues.apache.org/jira/browse/FLINK-11900
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.7.2
> Reporter: Mario Georgiev
> Assignee: frank wang
> Priority: Major
>
> Hello guys,
> I've discovered that when deploying the job cluster on Kubernetes, the Job Cluster Manager seems sensitive about the placement of arguments.
> For instance if i put the savepoint argument last, it never reads it.
> For instance if arguments are :
> {code:java}
> job-cluster --job-classname <classname> --fromSavepoint <savepointPath> --allowNonRestoredState does not pick the savepoint path and does not start from it
> job-cluster --fromSavepoint <savepointPath> -n --job-classname <classname> -p works for savepoint retrieval{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)