flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhenzhong Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4308) Allow uploaded jar directory to be configurable
Date Tue, 02 Aug 2016 21:58:20 GMT

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

Zhenzhong Xu commented on FLINK-4308:

The proposal is to introduce a new optional config "jobmanager.web.uploaddir". If specified
job jar will be uploaded and read from the predefined directory. If not specified, it falls
back to the old behavior which is to create a dynamic directory under whatever specified "jobmanager.web.tmpdir"
(or default tmp if this is not specified either).

Change is simple, let me know if this sounds good I an send a PR in.

> Allow uploaded jar directory to be configurable 
> ------------------------------------------------
>                 Key: FLINK-4308
>                 URL: https://issues.apache.org/jira/browse/FLINK-4308
>             Project: Flink
>          Issue Type: Improvement
>          Components: Webfrontend
>            Reporter: Zhenzhong Xu
>            Priority: Minor
> I notice sometimes it's preferable to have uploaded jars to be put into a configurable
directory location instead only have it at runtime. In this case we can pre-load the directory
with jars in a docker image and allows us to leverage the jobmanager restful interface to
start/kill jobs.
> WebRuntimeMonitor.java
> String uploadDirName = "flink-web-upload-" + UUID.randomUUID();
> this.uploadDir = new File(getBaseDir(config), uploadDirName);

This message was sent by Atlassian JIRA

View raw message