Hi Sen Sun,
The question is already resolved. You can find the entire email thread here:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/flink-list-and-flink-run-commands-timeout-td22826.html
Best,
Gary
On Wed, Feb 27, 2019 at 7:55 AM sen wrote:
> Hi Aneesha:
>
>
Hi Aneesha:
I am also facing the same problem.When I turn on the HA on yarn ,it
will get the same exception. While I turn off the Ha configuration ,it works
fine.
I want to know that what did you do to deal with the problem?
Thanks!
Sen Sun
--
Sent from:
Thanks Chesnay! The exception is gone now.
On 03-Dec-2018, at 5:22 PM, Chesnay Schepler wrote:Based on the stacktrace the client is not running in legacy mode; please check the client flink-conf.yaml.
Thanks Chesnay! The exception is gone now.
> On 03-Dec-2018, at 5:22 PM, Chesnay Schepler wrote:
>
> Based on the stacktrace the client is not running in legacy mode; please
> check the client flink-conf.yaml.
Based on the stacktrace the client is not running in legacy mode; please
check the client flink-conf.yaml.
On 03.12.2018 12:10, Aneesha Kaushal wrote:
Hello,
I am facing the same Timeout exception, at flink run and flink list
commands when I am trying to deploy jobs in Flink 1.6 in “legacy"
Hello,
I am facing the same Timeout exception, at flink run and flink list commands
when I am trying to deploy jobs in Flink 1.6 in “legacy" mode.
We are planning to run in legacy mode because after upgrading from Flink 1.3 to
Flink 1.6, flink job was not getting distributed across task
Hi Jason,
>From the stacktrace it seems that you are using the 1.4.0 client to list
jobs
on a 1.5.x cluster. This will not work. You have to use the 1.5.x client.
Best,
Gary
On Wed, Sep 5, 2018 at 5:35 PM, Jason Kania wrote:
> Hello,
>
> Thanks for the response. I had already tried setting
Hello,
Thanks for the response. I had already tried setting the log level to debug in
log4j-cli.properties, logback-console.xml, and log4j-console.properties but no
additional relevant information comes out. On the server, all that comes out
are zookeeper ping responses:
2018-09-05 15:16:56,786
Please enable DEBUG logging for the client and TRACE logging for the
cluster.
For the client, look for log messages starting with "Sending request
of", this will contain the host and port that requests are sent to by
the client. Verify that these are correct and match the host/port that
you
I have upgraded from Flink 1.4.0 to Flink 1.5.3 with a three node cluster
configured with HA. Now I am encountering an issue where the flink command line
operations timeout. The exception generated is very poor because it only
indicates a timeout and not the reason or what it was trying to do:
10 matches
Mail list logo