[ https://issues.apache.org/jira/browse/FLINK-31518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705330#comment-17705330 ]
Weihua Hu commented on FLINK-31518: ----------------------------------- [~prabhujoseph] how about update configuration with the real rest port after webmonitor start in DefaultDispatcherResourceManagerComponentFactory. Then in your own service use this configuration to create a ClientHighAvailabilityServices to retrieve the rest address. > HighAvailabilityServiceUtils resolves wrong webMonitorAddress in Standalone > mode > -------------------------------------------------------------------------------- > > Key: FLINK-31518 > URL: https://issues.apache.org/jira/browse/FLINK-31518 > Project: Flink > Issue Type: Bug > Components: Runtime / Configuration, Runtime / REST > Affects Versions: 1.16.0, 1.17.0, 1.16.1, 1.17.1 > Reporter: Vineeth Naroju > Priority: Major > > {{HighAvailabilityServiceUtils#createHighAvailabilityServices()}} in > {{HighAvailabilityMode.NONE}} mode uses > {{HighAvailabilityServiceUtils#getWebMonitorAddress()}} to get web monitor > address. > {{HighAvailabilityServiceUtils#getWebMonitorAddress()}} reads only from > {{rest.port}} in {{flink-conf.yaml}} . If {{rest.port}} is not enabled, then > it returns {{0}} port number. It should dynamically fetch port number if > {{rest.port}} is disabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)