[jira] [Created] (FLINK-17747) PackagedProgram' extractedTempLibraries and jarfiles may be duplicate

2020-05-15 Thread lisen (Jira)
lisen created FLINK-17747:
-

 Summary: PackagedProgram' extractedTempLibraries and jarfiles may 
be duplicate
 Key: FLINK-17747
 URL: https://issues.apache.org/jira/browse/FLINK-17747
 Project: Flink
  Issue Type: Bug
  Components: Client / Job Submission
Affects Versions: 1.10.0
Reporter: lisen
 Fix For: 1.10.0


When i submit a flink app with a fat jar, PackagedProgram will extracted temp 
libraries by the fat jar, and add to pipeline.jars, and the pipeline.jars 
contains  fat jar and temp libraries. I don't think we should add fat jar to 
the pipeline.jars if extractedTempLibraries is not empty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-17746) PackagedProgram' extractedTempLibraries and jarfiles may be duplicate

2020-05-15 Thread lisen (Jira)
lisen created FLINK-17746:
-

 Summary: PackagedProgram' extractedTempLibraries and jarfiles may 
be duplicate
 Key: FLINK-17746
 URL: https://issues.apache.org/jira/browse/FLINK-17746
 Project: Flink
  Issue Type: Bug
  Components: Client / Job Submission
Affects Versions: 1.10.0
Reporter: lisen
 Fix For: 1.10.0


When i submit a flink app with a fat jar, PackagedProgram will extracted temp 
libraries by the fat jar, and add to pipeline.jars, and the pipeline.jars 
contains  fat jar and temp libraries. I don't think we should add fat jar to 
the pipeline.jars if extractedTempLibraries is not empty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-17745) PackagedProgram' extractedTempLibraries and jarfiles may be duplicate

2020-05-15 Thread lisen (Jira)
lisen created FLINK-17745:
-

 Summary: PackagedProgram' extractedTempLibraries and jarfiles may 
be duplicate
 Key: FLINK-17745
 URL: https://issues.apache.org/jira/browse/FLINK-17745
 Project: Flink
  Issue Type: Bug
  Components: Client / Job Submission
Affects Versions: 1.10.0
Reporter: lisen
 Fix For: 1.10.0


When i submit a flink app with a fat jar, PackagedProgram will extracted temp 
libraries by the fat jar, and add to pipeline.jars, and the pipeline.jars 
contains  fat jar and temp libraries. I don't think we should add fat jar to 
the pipeline.jars if extractedTempLibraries is not empty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-17744) StreamContextEnvironment#execute cannot be call JobListener#onJobExecuted

2020-05-15 Thread lisen (Jira)
lisen created FLINK-17744:
-

 Summary: StreamContextEnvironment#execute cannot be call 
JobListener#onJobExecuted
 Key: FLINK-17744
 URL: https://issues.apache.org/jira/browse/FLINK-17744
 Project: Flink
  Issue Type: Bug
  Components: Client / Job Submission
Affects Versions: 1.10.0
Reporter: lisen
 Fix For: 1.10.0


When I register a jobListener  to stream environment. I want  
JobListener#onJobExecuted is executed when job was finished or cancelled. But 
in StreamContextEnvironment, the method  JobListener#onJobExecuted is not 
called now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-17742) Blob file not removed after task was cancelled in standalone mode

2020-05-15 Thread lisen (Jira)
lisen created FLINK-17742:
-

 Summary: Blob file not removed after task was cancelled in 
standalone mode
 Key: FLINK-17742
 URL: https://issues.apache.org/jira/browse/FLINK-17742
 Project: Flink
  Issue Type: Bug
  Components: API / Core
Affects Versions: 1.10.0
Reporter: lisen
 Fix For: 1.10.0


In standalone mode, i submit a job with my user jars, we know, the jars will be 
upload to blob server, and the TaskExecutor will be download blob file to 
local, So, jobmanager node and taskmanager node have two blob file at the same 
time. But the situation is,when the job finished or canceled, jobmanager node's 
blob file is removed and taskmanager is not. I think there is a risk of 
bursting here.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-14542) YarnConfiguration initialization problem

2019-10-28 Thread lisen (Jira)
lisen created FLINK-14542:
-

 Summary: YarnConfiguration initialization problem
 Key: FLINK-14542
 URL: https://issues.apache.org/jira/browse/FLINK-14542
 Project: Flink
  Issue Type: Bug
  Components: Client / Job Submission
Affects Versions: 1.9.0
Reporter: lisen
 Fix For: 1.10.0


In the YarnResourceManager class,yarnConfig initialization result is not the 
desired result,code is:this.yarnConfig = new YarnConfiguration(),the added 
resource is the resource in my classpath,instead of the yarn configuration of 
this machine.I deleted the yarn.site in the classpath and it is ok. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)