[
https://issues.apache.org/jira/browse/FLINK-9255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456371#comment-16456371
]
Edward Rojas commented on FLINK-9255:
-------------------------------------
I was not aware of that change. Effectively using the rest port solves the
issue.
I guess we'll expect an update on the docs about this.
Thanks
> Regression - Flink CLI -m,--jobmanager option not working
> ----------------------------------------------------------
>
> Key: FLINK-9255
> URL: https://issues.apache.org/jira/browse/FLINK-9255
> Project: Flink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.5.0
> Environment: Local environment - Branch release-1.5
> Reporter: Edward Rojas
> Priority: Major
> Labels: cli, regression
>
> Every time the flink CLI is called with the -m option to specify the
> jobmanager address, the CLI is stuck on "Waiting for response..." and the
> Jobmanager reports the following error:
> WARN akka.remote.transport.netty.NettyTransport - Remote connection to
> [/x.x.x.x:xxxx] failed with
> org.apache.flink.shaded.akka.org.jboss.netty.handler.codec.frame.TooLongFrameException:
> Adjusted frame length exceeds 10485760: 1195725860 - discarded
> The error occurs even when run locally and try something like "flink list -m
> localhost:6123". But "flink list" works as expected.
> I'm using the version from the "release-1.5" branch.
>
> It seems like the commit introducing the regression is
> [47909f4|https://github.com/apache/flink/commit/47909f466b9c9ee1f4caf94e9f6862a21b628817]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
