Re: Using port ranges to connect with the Flink Client

2019-01-06 Thread Joshua Fan
Hi Chesnay Yes, RestClusterClient is used in our company when using flink 1.7. It can do almost everything except to get the ClusterOverview when I want to get summary information on a session cluster. Finally, I manually trigger a http get request to the cluster to do that. If RestClusterClient

Re: Using port ranges to connect with the Flink Client

2019-01-04 Thread Gyula Fóra
Hi, Thanks Chesnay my problem was fixed it was related to enabling port ranges for the rest client it turned out. Gyula On Fri, 4 Jan 2019 at 10:26, Chesnay Schepler wrote: > @Gyula: From what I can tell your custom client is still relying on > akka, and should be using the RestClusterClient

Re: Using port ranges to connect with the Flink Client

2019-01-02 Thread Joshua Fan
Hi, Gyula I met a similar situation. We used flink 1.4 before, and everything is ok. Now, we upgrade to flink 1.7 and use non-legacy mode, there seems something not ok, it all refers to that it is impossible get the jobmanagerGateway at client side. When I create a cluster without a job, I

Re: Using port ranges to connect with the Flink Client

2018-12-05 Thread Gyula Fóra
Ah, it seems to be something with the custom flink client build that we run... Still dont know why but if I use the normal client once the job is started it works. Gyula Gyula Fóra ezt írta (időpont: 2018. dec. 5., Sze, 9:50): > I get the following error when trying to savepoint a job for

Using port ranges to connect with the Flink Client

2018-12-04 Thread Gyula Fóra
Hi! We have been running Flink on Yarn for quite some time and historically we specified port ranges so that the client can access the cluster: yarn.application-master.port: 100-200 Now we updated to flink 1.7 and try to migrate away from the legacy execution mode but we run into a problem that