flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kostas Kloudas (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-18048) "--host" option could not take effect for standalone application cluster
Date Fri, 05 Jun 2020 12:25:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-18048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kostas Kloudas updated FLINK-18048:
-----------------------------------
    Fix Version/s: 1.12.0

> "--host" option could not take effect for standalone application cluster
> ------------------------------------------------------------------------
>
>                 Key: FLINK-18048
>                 URL: https://issues.apache.org/jira/browse/FLINK-18048
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Scripts
>    Affects Versions: 1.11.0, 1.10.2
>            Reporter: Yang Wang
>            Assignee: Yang Wang
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.11.0, 1.10.2, 1.12.0
>
>
> When we use the following command to start a Flink application cluster, the specified
hostname could not take effect. The root cause is {{HOST_OPTION}} is not added to options
in {{StandaloneApplicationClusterConfigurationParserFactory}}. It will be a critical issue
when we deploy Flink on container environment. Because users usually want to specify a given
hostname.
>  
> {code:java}
> ./bin/standalone-job.sh start --host external-hostname --job-classname org.apache.flink.streaming.examples.join.WindowJoin
> {code}
>  
> For the old {{StandaloneJobClusterConfigurationParserFactory}}, it has the same issue.



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

Mime
View raw message