HI Aljoscha
I was able to get the ClusterClient and Accumulators using following:
DefaultCLI defaultCLI = new DefaultCLI();
CommandLine line = new DefaultParser().parse(new Options(), new
String[]{}, true);
ClusterClient clusterClient = defaultCLI.retrieveCluster(line,configuration);
Regards
S
Hi,
there is ClusterClient.getAccumulators(JobID jobID) which should be able to
get the accumulators for a running job. If you can construct a
ClusterClient that should be a good solution.
Cheers,
Aljoscha
On Wed, 21 Sep 2016 at 21:15 Chawla,Sumit wrote:
> Hi Sean
>
> My goal here is to get Use
Hi Sean
My goal here is to get User Accumulators. I know there exists the REST
Calls. But since i am running my code in the same JVM, i wanted to avoid
go over HTTP. I saw this code in JobAccumulatorsHandler and tried to use
this. Would you suggest some alternative approach to avoid this over
> To: dev@flink.apache.org
> Sent: Wednesday, September 21, 2016 11:08 AM
> Subject: Re: Get Flink ExecutionGraph Programmatically
>
> Hi Chesney
>
> I am actually running this code in the same JVM as the WebInterface and
> JobManager. I am programmatically, starting the JobManage
Between two different actor systems in the same JVM, messages are still
serialized (they go through a local socket, I think).
Getting the execution graph is not easily possible, and not intended, as it
actually contains RPC resources, etc.
What do you need from the execution graph? Maybe there is
my previous config & continued
with turning knobs that wouldn't cause Akka exceptions.Thanks+regardsAmir-
From: "Chawla,Sumit"
To: dev@flink.apache.org
Sent: Wednesday, September 21, 2016 11:08 AM
Subject: Re: Get Flink ExecutionGraph Programmatically
Hi Chesney
Hi Chesney
I am actually running this code in the same JVM as the WebInterface and
JobManager. I am programmatically, starting the JobManager. and then
running this code in same JVM to query metrics. Only difference could be
that i am creating a new Akka ActorSystem, and ActorGateway. Not sure
Hello,
this is a rather subtle issue you stumbled upon here.
The ExecutionGraph is not serializable. The only reason why the
WebInterface can access it is because it runs in the same JVM as the
JobManager.
I'm not sure if there is a way for what you are trying to do.
Regards,
Chesnay
On 21
