This is expected behavior. Since jar A is on the classpath you are able
to access the entry-class of said jar. When you specify the jar id all
that does is put another jar on the classpath; it is not enforce that
the entry-class is loaded from said jar.
On 08/01/2022 16:45, Qihua Yang wrote:
Hi Yun,
Thank you for your reply! testB.jar doesn't have the same entry class as
testA.jar.
So is it expected behavior? What is the theory behind?
Thanks,
Qihua
On Fri, Jan 7, 2022 at 4:27 PM Yun Gao wrote:
>
> Hi Qihua
>
> Sorry may I double confirm that whether the entry class exists in both
Hi Qihua
Sorry may I double confirm that whether the entry class exists in both testA
and testB?
IF testA.jar is included on startup, it would be loaded in the parent
classloader, which
is the parent classloader for the user classloader that loads testB. Thus at
least if the
entry-class is ex
Hi White,
Can you describe your problem in more detail?
* What is your Flink version?
* How do you deploy the job (application / session cluster), (Kubernetes,
Docker, YARN, ...)
* What kind of job are you running (DataStream, Table/SQL, DataSet)?
Best, Fabian
Am Mo., 20. Juli 2020 um 08:42 Uhr
:*Chesnay Schepler
*Sent:* 11 May 2020 13:20
*To:* Tomasz Dudziak ; user@flink.apache.org
*Subject:* Re: Flink REST API side effect?
This is expected, the backing data structure is cached for a while so
we never hammer the JobManager with requests.
IIRC this is controlled via "web.refresh-int
@flink.apache.org
Subject: Re: Flink REST API side effect?
This is expected, the backing data structure is cached for a while so we never
hammer the JobManager with requests.
IIRC this is controlled via "web.refresh-interval", with the default being 3
seconds.
On 11/05/2020 14:10, Tomasz Dud
This is expected, the backing data structure is cached for a while so we
never hammer the JobManager with requests.
IIRC this is controlled via "web.refresh-interval", with the default
being 3 seconds.
On 11/05/2020 14:10, Tomasz Dudziak wrote:
Hi,
I found an interesting behaviour of the R
Hi Vipul,
We are aware of YARN-2031. There are some ideas how to workaround it, which
are tracked here:
https://issues.apache.org/jira/browse/FLINK-9478
At the moment you have the following options:
1. Find out the master's address from ZooKeeper [1] and issue the HTTP
request against t
ication -list”*
>
>
>
> Thanks a lot.
>
>
>
> Regards,
>
> Raja.
>
>
>
> *From: *Gary Yao
> *Date: *Friday, February 9, 2018 at 9:25 AM
> *To: *Raja Aravapalli
> *Cc: *"user@flink.apache.org"
> *Subject: *Re: [EXTERNAL] Re: Flink REST AP
received from Yarn Client using the
command “yarn application -list”
Thanks a lot.
Regards,
Raja.
From: Gary Yao
Date: Friday, February 9, 2018 at 9:25 AM
To: Raja Aravapalli
Cc: "user@flink.apache.org"
Subject: Re: [EXTERNAL] Re: Flink REST API
Hi Raja,
Can you tell me the API call th
gt;
>
> Regards,
>
> Raja.
>
>
>
> *From: *Gary Yao
> *Date: *Friday, February 2, 2018 at 10:20 AM
> *To: *Raja Aravapalli
> *Cc: *"user@flink.apache.org"
> *Subject: *[EXTERNAL] Re: Flink REST API
>
>
>
> Hi Raja,
>
>
>
> The r
2, 2018 at 10:20 AM
To: Raja Aravapalli
Cc: "user@flink.apache.org"
Subject: [EXTERNAL] Re: Flink REST API
Hi Raja,
The registered tracking URL of the YARN application can be used to issue HTTP
requests against the REST API. You can retrieve the URL by using the YARN
client:
yarn a
Hi Raja,
The registered tracking URL of the YARN application can be used to issue
HTTP
requests against the REST API. You can retrieve the URL by using the YARN
client:
yarn application -list
In the output, the rightmost column shows the URL, e.g.,
Application-Id ... Trac
Sorry guys,
in the previous message, when I talked about the task managers performance,
I meant *Jobmanager* performance
Francisco Gonzalez wrote
> Hi guys,
>
> After investigating a bit more about this topic, we found a solution
> adding
> a small change in the Flink-1.3.2 source code.
>
> W
Hi guys,
After investigating a bit more about this topic, we found a solution adding
a small change in the Flink-1.3.2 source code.
We found that the issue occurred when different threads tried to build the
Tuple2 object at the same time (due to they use the
static ExecutionEnvironmnet variable
Hi,
Unfortunately, the FLIP-6 efforts are taking longer than expected and we won't
have those changes to the REST API in the 1.4 release (which should happen in
about a month). We are planning to very quickly release 1.5 after that, with
the changes to the REST API.
The only work-around I can
Hello,
Going back on this thread, quick question: Will this be supported in next Flink
version? If not, when is it expected to be included?
Regards
On 8 Aug 2017, at 15:46, Aljoscha Krettek
mailto:aljos...@apache.org>> wrote:
I quickly talked to Till about this. The new JobManager, once FLIP
I quickly talked to Till about this. The new JobManager, once FLIP-6 is
implemented, will have a new REST endpoint that allows submitting a JobGraph
directly. With this, we no longer have to execute the user main() method in the
WebRuntimeMonitor (which is a component that the current JobManager
Aha ok… Thanks for your answer Eron.
Regards
On 7 Aug 2017, at 19:04, Eron Wright
mailto:eronwri...@gmail.com>> wrote:
When you submit a program via the REST API, the main method executes inside the
JobManager process.Unfortunately a static variable is used to establish the
execution env
When you submit a program via the REST API, the main method executes inside
the JobManager process.Unfortunately a static variable is used to
establish the execution environment that the program obtains from
`ExecutionEnvironment.getExecutionEnvironment()`. From the stack trace it
appears that
20 matches
Mail list logo
