ver
> > needs to cache
> > buffers for blocked channels during alignment. We also illustrated such
> > changes in release notes for attention by link [1].
> >
> > [1]
> >
> https://github.com/apache/flink/pull/12699/files#diff-eaa874e007e88f283e96de2d61cc
changes in release notes for attention by link [1].
[1]
https://github.com/apache/flink/pull/12699/files#diff-eaa874e007e88f283e96de2d61cc4140R174
Best,
Zhijiang
----------
From:Thomas Weise
Send Time:2020年6月24日(星期三) 06:51
To:dev
Cc:zhijiang
Subjec
eed
> >> up checkpoint somehow. The upstream side would block sending any
> following
> >> buffers after sending the barrier until receiving the alignment
> >> notification from downstream side. Therefore, the downstream side never
> >> needs to cache
> >> buffers for blocked channels during a
ache
>> buffers for blocked channels during alignment. We also illustrated such
>> changes in release notes for attention by link [1].
>>
>> [1]
>> https://github.com/apache/flink/pull/12699/files#diff-eaa874e007e88f283e96de2d61cc4140R174
>>
>> Best,
>> Zhijiang
>> ---
nels during alignment. We also illustrated such
> changes in release notes for attention by link [1].
>
> [1]
> https://github.com/apache/flink/pull/12699/files#diff-eaa874e007e88f283e96de2d61cc4140R174
>
> Best,
> Zhijiang
> ----------
https://github.com/apache/flink/pull/12699/files#diff-eaa874e007e88f283e96de2d61cc4140R174
Best,
Zhijiang
--
From:Thomas Weise
Send Time:2020年6月24日(星期三) 06:51
To:dev
Cc:zhijiang
Subject:Re: [ANNOUNCE] Apache Flink 1.11.0, release can
Hi,
Thanks for putting together the RC!
I have some preliminary feedback from testing with commit
934f91ead00fd658333f65ffa37ab60bd5ffd99b
An internal benchmark application that reads from Kinesis and checkpoints
~12GB performs comparably to 1.10.1
There were a few issues hit upgrading our
/dev/flink/flink-1.11.0-rc2/
Best,
Zhijiang
--
From:Fabian Paul
Send Time:2020年6月23日(星期二) 15:41
To:Zhijiang ; dev
Cc:zhijiang ; pnowojski
Subject:Re: [ANNOUNCE] Apache Flink 1.11.0, release candidate #2
Hi,
Thanks again
I tested RC2 successfully on EMR with 160 cores across 5 nodes using the
performance benchmark [1] with s3 file backend.
I used different backpressure settings to compare aligned and unaligned
checkpoints on 1.11-rc2 and aligned checkpoints of 1.10.1. I saw no errors
and no regressions (rather we
Hi,
Thanks again for uploading the missing artifacts. Unfortunately this rc does
not fully compile due to [1].
Would it be possible for testing purposed to quickly include this fix into the
rc or do you think it is necessary to open a complete new one?
[1]
://repository.apache.org/content/repositories/orgapacheflink-1375/
Best,
Zhijiang
--
From:Zhijiang
Send Time:2020年6月22日(星期一) 18:34
To:Fabian Paul ; dev
Cc:zhijiang ; pnowojski
Subject:Re: [ANNOUNCE] Apache Flink 1.11.0, release candidate #2
Subject:Re: [ANNOUNCE] Apache Flink 1.11.0, release candidate #2
Hi,
Thanks for the great efforts in preparing the second rc. I was just going
through the published artifacts and it seems that some are missing in the
latest release.
In comparison you can look at
https://repository.apache.org
Hi,
Thanks for the great efforts in preparing the second rc. I was just going
through the published artifacts and it seems that some are missing in the
latest release.
In comparison you can look at
https://repository.apache.org/content/repositories/orgapacheflink-1370/org/apache/flink/
Thanks a lot for creating another RC.
The good news first: WordCount works on my Mac :)
I didn't find this information in the email: This is the commit the RC is
based on:
https://github.com/apache/flink/commit/c4132de4a50ab9b8f653c69af1ba15af44ff29a2
Additionally, I've created [1] a docker
Hi all,
Apache Flink-1.11.0-RC2 has been created. It has all the artifacts that we
would typically have for a release.
This RC might have still a couple of missing licensing notices (like the
one mentioned by Jingsong Li), but as for today morning, there were no open
release blocking bugs. No
Hi Piotr and Zhijiang,
I merged three commits in 1 hour ago:
one blocker: 0dafcf8792220dbe5b77544261f726a566b054f5
two critical issues:
1830c1c47b8a985ec328a7332e92d21433c0a4df
80fa0f5c5b8600f4b386487f267bde80b882bd07
I have synced with Zhijiang, they were merged after RC2 branch cutting. So
RC2
Hi all,
I would like to give an update about the RC2 status. We are now waiting for
a green azure build on one final bug fix before creating RC2. This bug fix
should be merged late afternoon/early evening Berlin time, so RC2 will be
hopefully created tomorrow morning. Until then I would ask to
17 matches
Mail list logo
