I guess it is a jm internal error which crashes the dispatcher or race
condition so that the returning future never completed, possibly related to
jdk bug. But again, never have a log in the case I cannot conclude anything.
Best,
tison.
tison 于2020年1月22日周三 上午10:49写道：
> It is a known issue repo
It is a known issue reported multiple times that if you are in an early jdk
1.8.x version, upgrade the bugfix version and the issue will vanish.
I don't ever have a log on jm side when this issue reported so I'm sorry
unable to explain more...
Best,
tison.
Yang Wang 于2020年1月22日周三 上午10:46写道：
>
The "web.timeout" will be used for all web monitor asynchronous operations,
including the
"DispatcherGateway.submitJob" in the "JobSubmitHandler".
So when you increase the timeout, does it still could not work?
Best,
Yang
satya brat 于2020年1月21日周二 下午8:57写道：
> How does web.timeout help hear?? The
How does web.timeout help hear?? The issue is with respect to aka
dispatched timing out. The job is submitted to the task managers but the
response doesn't reach the client.
On Tue, Jan 21, 2020 at 12:34 PM Yang Wang wrote:
> Hi satya,
>
> Maybe the job has been submitted to Dispatcher successfu
Hi satya,
Maybe the job has been submitted to Dispatcher successfully and the
internal submitting job takes
too long time(more than 10s). So it failed with timeout. Could you please
set the `web.timeout: 3`
and run again?
Best,
Yang
satya brat 于2020年1月20日周一 下午4:34写道：
> I am using standal
I am using standalone cluster of Flink with 1 jobManager and n
taskManagers. When I try to submit a job via command line, the job
submission fails with error message as
org.apache.flink.client.program.ProgramInvocationException: Could not
submit job (JobID: f839aefee74aa4483ce8f8fd2e49b69e).
On jo
