[
https://issues.apache.org/jira/browse/FLINK-21038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21038:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
