[
https://issues.apache.org/jira/browse/FLINK-21038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327400#comment-17327400
]
Flink Jira Bot commented on FLINK-21038:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> jobmanager.sh may misinterpret webui-port argument
> --------------------------------------------------
>
> Key: FLINK-21038
> URL: https://issues.apache.org/jira/browse/FLINK-21038
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Scripts
> Affects Versions: 1.9.0
> Reporter: Chesnay Schepler
> Priority: Major
> Labels: stale-major
>
> The usage description for {{jobmanager.sh}} is as follows:
> {code}
> Usage: jobmanager.sh ((start|start-foreground) [host]
> [webui-port])|stop|stop-all
> {code}
> It shows both {{host}} and {{webui-port}} as _separate_ optional arguments,
> however we hard-code the positions of these parameters:
> {code}
> STARTSTOP=$1
> HOST=$2 # optional when starting multiple instances
> WEBUIPORT=$3 # optional when starting multiple instances
> {code}
> As such you cannot set the webui.port without also setting some dummy host
> argument.
> I'm wondering whether we could not remove these in favor of dynamic
> properties.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
