Hi Yang Wang:
I meet the question “flink job failed because Am connection is timeout but
application still running via yarn-per-job mode” the same as
https://issues.apache.org/jira/browse/FLINK-18891
I try to set execution.attached to false,Will this cause other
problems？I worry
Hi weifeng,
The reason why your settings in flink-conf.yaml do not take effect is that
we override the
"execution.attached" in "FlinkYarnSessionCli#applyDescriptorOptionToConfig"
based
on the cli option. If the "-d" is specified, "execution.attached" will be
set to false. Otherwise,
it is true.
Hi Kostas,
Thanks for starting this discussion. The first part of this FLIP: "Batch vs
Streaming Scheduling" looks reasonable to me.
However, there is another dimension I think we should also take into
consideration, which is whether checkpointing is enabled.
This option is orthogonal (but not
Xin Wang created FLINK-18969:
Summary: Source code build error: Could not resolve dependencies
for project org.apache.flink:flink-oss-fs-hadoop:jar:1.12-SNAPSHOT
Key: FLINK-18969
URL:
Hi Devs,
I would like to start a formal discussion about "FLIP-135 Approximate
Task-Local Recovery" [1] which supports approximate single task failure
recovery without restarting the entire streaming job.
Flink is no longer a pure streaming engine as it was born and has been
extended to fit into
Zixuan Rao created FLINK-18968:
--
Summary: Translate StateFun homepage to Chinese
Key: FLINK-18968
URL: https://issues.apache.org/jira/browse/FLINK-18968
Project: Flink
Issue Type: Task
