[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-major, stale-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.3.4#803005)
