[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-17472: --- Priority: Minor (was: Major) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: Roc Marshal >Priority: Minor > Labels: auto-deprioritized-major > Attachments: demo.jpeg > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the external link [Simple outline of the > Yarn-Env API（Per-Job > Mode)|https://gitee.com/RocMarshal/resources4link/blob/master/README.md] .the > parameter named 'env' containes all the operators about job ,like > sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-17472: --- Labels: auto-deprioritized-major (was: stale-major) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: Roc Marshal >Priority: Major > Labels: auto-deprioritized-major > Attachments: demo.jpeg > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the external link [Simple outline of the > Yarn-Env API（Per-Job > Mode)|https://gitee.com/RocMarshal/resources4link/blob/master/README.md] .the > parameter named 'env' containes all the operators about job ,like > sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-17472: --- Labels: stale-major (was: ) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: Roc Marshal >Priority: Major > Labels: stale-major > Attachments: demo.jpeg > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the external link [Simple outline of the > Yarn-Env API（Per-Job > Mode)|https://gitee.com/RocMarshal/resources4link/blob/master/README.md] .the > parameter named 'env' containes all the operators about job ,like > sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: demo.jpeg > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.jpeg > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the external link [Simple outline of the > Yarn-Env API（Per-Job > Mode)|https://gitee.com/RocMarshal/resources4link/blob/master/README.md] .the > parameter named 'env' containes all the operators about job ,like > sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Description: Expect to have such a mode of submission. Build the task directly in the Environment, and then submit the task in yarn mode. Just like RemoteStreamEnvironment, as long as you specify the parameters of the yarn cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, you can use the topology built by Env to submit the task . This submission method is best to minimize the transmission of resources required by yarn to start flink-jobmanager and taskmanagerrunner to ensure that flink can deploy tasks on the yarn cluster as quickly as possible. The simple demo as shown in the external link [Simple outline of the Yarn-Env API（Per-Job Mode)|https://gitee.com/RocMarshal/resources4link/blob/master/README.md] .the parameter named 'env' containes all the operators about job ,like sources,maps,etc.. was: Expect to have such a mode of submission. Build the task directly in the Environment, and then submit the task in yarn mode. Just like RemoteStreamEnvironment, as long as you specify the parameters of the yarn cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, you can use the topology built by Env to submit the task . This submission method is best to minimize the transmission of resources required by yarn to start flink-jobmanager and taskmanagerrunner to ensure that flink can deploy tasks on the yarn cluster as quickly as possible. The simple demo as shown in the attachment .the parameter named 'env' containes all the operators about job ,like sources,maps,etc.. > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the external link [Simple outline of the > Yarn-Env API（Per-Job > Mode)|https://gitee.com/RocMarshal/resources4link/blob/master/README.md] .the > parameter named 'env' containes all the operators about job ,like > sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: demo.jpeg > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: (was: demo.jpeg) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: (was: demo.png) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: (was: demo.jpeg) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: demo.jpeg > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Labels: (was: starter) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Labels: starter (was: ) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Labels: starter > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aljoscha Krettek updated FLINK-17472: - Docs Text: (was: There may be many details about this new feature that we have to pay attention to. As discussed in jira below. https://issues.apache.org/jira/browse/FLINK-14964; https://issues.apache.org/jira/browse/FLINK-13938; https://issues.apache.org/jira/browse/FLINK-17412) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: demo.png > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: (was: demo.png) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: demo.png > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: (was: demo.png) > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RocMarshal updated FLINK-17472: --- Attachment: demo.png > StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode > > > Key: FLINK-17472 > URL: https://issues.apache.org/jira/browse/FLINK-17472 > Project: Flink > Issue Type: New Feature > Components: Client / Job Submission, Deployment / YARN >Affects Versions: 1.10.0 >Reporter: RocMarshal >Priority: Major > Attachments: demo.png > > > Expect to have such a mode of submission. Build the task directly in the > Environment, and then submit the task in yarn mode. Just like > RemoteStreamEnvironment, as long as you specify the parameters of the yarn > cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, > you can use the topology built by Env to submit the task . > This submission method is best to minimize the transmission of resources > required by yarn to start flink-jobmanager and taskmanagerrunner to ensure > that flink can deploy tasks on the yarn cluster as quickly as possible. > The simple demo as shown in the attachment .the parameter named 'env' > containes all the operators about job ,like sources,maps,etc.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
