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 can provide a similar interface will be good.
Yours Joshua On Fri, Jan 4, 2019 at 5:28 PM Gyula Fóra <gyula.f...@gmail.com> wrote: > 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 <ches...@apache.org> wrote: > >> @Gyula: From what I can tell your custom client is still relying on >> akka, and should be using the RestClusterClient instead. >> >> @Joshua: Are you by change using the ClusterClient directly? Unless >> you're working with legacy clusters, for 1.5+ you should use the >> RestClusterClient instead. >> >> On 03.01.2019 08:32, Joshua Fan wrote: >> > 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 describe the cluster, flink will throw the same exception as >> > you pointed out. When I submit a job, I want to trigger a savepoint at >> > client side, it will also throw the same exception. >> > >> > Don't know why in non-legacy mode,flink will not write back the leader >> > info into zookeeper in the path of >> > /flink/app_99999_000/leader/000000000/job _manager_lock. This causes >> > all the operations fail when using the jobmanagerGateway method in >> > ClusterClient. >> > >> > Hope someone can explain how to do this in a non-legacy mode. >> > >> > Yours sincerely >> > Joshua >> >> >>
