[
https://issues.apache.org/jira/browse/FLINK-13750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919295#comment-16919295
]
TisonKun edited comment on FLINK-13750 at 8/30/19 9:55 AM:
-----------------------------------------------------------
Hi here. I noticed that {{ClusterClient#getClusterConnectionInfo}} works out of
expected in YARN scenario. In YARN scenario we set the port exactly to
WebMonitor's port.
{code:java}
final String host = appReport.getHost();
final int rpcPort = appReport.getRpcPort();
LOG.info("Found application JobManager host name '{}' and port '{}' from
supplied application id '{}'",
host, rpcPort, applicationId);
flinkConfiguration.setString(JobManagerOptions.ADDRESS, host);
flinkConfiguration.setInteger(JobManagerOptions.PORT, rpcPort);
flinkConfiguration.setString(RestOptions.ADDRESS, host);
flinkConfiguration.setInteger(RestOptions.PORT, rpcPort);
{code}
thus the interface never works as expected. I suspect this hasn't been found so
far because no one relies on it.
Given a further investigating all usages(omit used in logs, all under
scala-shell and thus remote executor) actually communicate with {{WebMonitor}}
instead of {{Dispatcher}}. I'd like to just remove this interface though.
was (Author: tison):
Hi here. I noticed that {{ClusterClient#getClusterConnectionInfo}} works our of
expected in YARN scenario. In YARN scenario we set the port exactly to
WebMonitor's port.
{code:java}
final String host = appReport.getHost();
final int rpcPort = appReport.getRpcPort();
LOG.info("Found application JobManager host name '{}' and port '{}' from
supplied application id '{}'",
host, rpcPort, applicationId);
flinkConfiguration.setString(JobManagerOptions.ADDRESS, host);
flinkConfiguration.setInteger(JobManagerOptions.PORT, rpcPort);
flinkConfiguration.setString(RestOptions.ADDRESS, host);
flinkConfiguration.setInteger(RestOptions.PORT, rpcPort);
{code}
thus the interface never works as expected. I suspect this doesn't find before
because no one relies on it.
Given a further investigating all usages(omit used in logs, all under
scala-shell and thus remote executor) actually communicate with {{WebMonitor}}
instead of {{Dispatcher}}. I'd like to just remove this interface though.
> Separate HA services between client-/ and server-side
> -----------------------------------------------------
>
> Key: FLINK-13750
> URL: https://issues.apache.org/jira/browse/FLINK-13750
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client, Runtime / Coordination
> Reporter: Chesnay Schepler
> Assignee: TisonKun
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, we use the same {{HighAvailabilityServices}} on the client and
> server. However, the client does not need several of the features that the
> services currently provide (access to the blobstore or checkpoint metadata).
> Additionally, due to how these services are setup they also require the
> client to have access to the blob storage, despite it never actually being
> used, which can cause issues, like FLINK-13500.
> [~Tison] Would be be interested in this issue?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
