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

Andrey Zagrebin edited comment on FLINK-11900 at 11/6/20, 2:19 PM:
-------------------------------------------------------------------

This does not look like a problem in the current Flink version. If I change 
options order and put 
{code:java}
--job-classname before --fromSavepoint{code}
e.g. in 
StandaloneApplicationClusterConfigurationParserFactoryTest#testEntrypointClusterConfigurationToConfigurationParsing,
 it does not break.

I am closing the issue for now. Please, reopen it if you still believe it is a 
problem.


was (Author: azagrebin):
This does not look like a problem in the current Flink version. If I change 
options order and put 
{code:java}
-job-classname before -fromSavepoint{code}
e.g. in 
StandaloneApplicationClusterConfigurationParserFactoryTest#testEntrypointClusterConfigurationToConfigurationParsing,
 it does not break.

I am closing the issue for now. Please, reopen it if you still believe it is a 
problem.

> 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
(v8.3.4#803005)

Reply via email to