Which version of Flink are you using? In the 1.2 SNAPSHOT version the
configuration for save points is changed:
https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/savepoints.html#configuration
Cheers,
Aljoscha
On Fri, 14 Oct 2016 at 19:03 Jason Brelloch wrote:
> It is a standalon
Hello,
For your first question:
> the number of tuples are same in both cases
I guess you mean the total number of tuples here, right? So this means
that you have fewer, but larger windows. Suppose that you have W
windows, each with S tuples. Then your total input has W * S tuples,
and your tota
Hi!
Looks to me that this is the following problem: The Decompression Streams
did not properly forward the "close()" calls.
It is in the lastest 1.2-SNAPSHOT, but did not make it into version 1.1.3.
The fix is in that pull request: https://github.com/apache/flink/pull/2581
I have pushed the fix
Hi guys,
I followed this guide
(https://ci.apache.org/projects/flink/flink-docs-release-1.2/quickstart/java_api_quickstart.html),
but I get an Exception if I run WordCount
/usr/lib/jvm/java-8-oracle/bin/java -Didea.launcher.port=7536
-Didea.launcher.bin.path=/home/marc/Programs/idea-IC-162.203
Sorry, I should have mentioned that. We are still running 1.0.1 version.
On Sun, Oct 16, 2016 at 5:08 AM, Aljoscha Krettek
wrote:
> Which version of Flink are you using? In the 1.2 SNAPSHOT version the
> configuration for save points is changed: https://ci.apache.
> org/projects/flink/flink-doc
Hi All,
Any feedback is highly appreciated.
Thanks.
Li
> On Oct 15, 2016, at 11:17 AM, Li Wang wrote:
>
> Hi all,
>
> As far as I know, a stateful operator will checkpoint its current state to a
> persistent storage when it receives all the barrier from all of its upstream
> operators. My q
Hi!
No, the operator does not need to pause processing input records while the
checkpointing of its state is in progress.
The checkpointing of operator state is asynchronous. The operator state does
not need to be immutable, since its a copy of the snapshot state that’s
checkpointed.
Regards,
Hi,
I am currently using flink 1.2 snapshot and instrumenting my pipeline with
flink metrics. One small suggestion I have is currently the Meter interface
only supports getRate() which is always the one minute rate.
It would great if all the rates (1 min, 5 min & 15 min) are exposed to get
a bett
Hi Gordon,
Thanks for your prompt reply.
So do you mean when we are about to checkpoint the state of an operator, we
first copy its state and then checkpoint the copied state while the operator
continues processing?
Thanks,
Li
> On Oct 17, 2016, at 11:10 AM, Tzu-Li (Gordon) Tai wrote:
>
> H
Users don’t need to explicitly make a copy of the state. Take checkpointing
instance fields as operator state for example [1].
You simply return your current state in `snapshotState()`, and Flink will take
care of snapshotting and persisting it to the state backend.
The persisting process does no
10 matches
Mail list logo
