Re:[VOTE] Release 1.5.0, release candidate #5

[sihua zhou]

Hi,
just one minor thing, I found the JIRA release notes seem a bit inconsistent 
with the this RC. For example, https://issues.apache.org/jira/browse/FLINK-9058 
hasn't been merged yet but included in the release notes, and 
https://issues.apache.org/jira/browse/FLINK-9070 has been merged but not 
included in the relase notes.


Best, Sihua




On 05/23/2018 09:18，Till Rohrmann wrote：
Hi everyone,

Please review and vote on the release candidate #5 for the version 1.5.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.0-rc5" [5],

Please use this document for coordinating testing efforts: [6]

Since the newly included fixes affect only individual components and are
covered by tests, I will shorten the voting period until tomorrow 5:30pm
CET. It is adopted by majority approval, with at least 3 PMC affirmative
votes.

Thanks,
Your friendly Release Manager

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12341764
[2] http://people.apache.org/~trohrmann/flink-1.5.0-rc5/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1160/
[5]
https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=841bfe4cceecc9cd6ad3d568173fdc0149a5dc9b
[6]
https://docs.google.com/document/d/1C1WwUphQj597jExWAXFUVkLH9Bi7-ir6drW9BgB8Ezo/edit?usp=sharing

Pro-tip: you can create a settings.xml file with these contents:



flink-1.5.0



flink-1.5.0


flink-1.5.0


https://repository.apache.org/content/repositories/orgapacheflink-1160/



archetype


https://repository.apache.org/content/repositories/orgapacheflink-1160/







And reference that in you maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

[VOTE] Release 1.5.0, release candidate #5

[Till Rohrmann]

Hi everyone,

Please review and vote on the release candidate #5 for the version 1.5.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.0-rc5" [5],

Please use this document for coordinating testing efforts: [6]

Since the newly included fixes affect only individual components and are
covered by tests, I will shorten the voting period until tomorrow 5:30pm
CET. It is adopted by majority approval, with at least 3 PMC affirmative
votes.

Thanks,
Your friendly Release Manager

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12341764
[2] http://people.apache.org/~trohrmann/flink-1.5.0-rc5/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1160/
[5]
https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=841bfe4cceecc9cd6ad3d568173fdc0149a5dc9b
[6]
https://docs.google.com/document/d/1C1WwUphQj597jExWAXFUVkLH9Bi7-ir6drW9BgB8Ezo/edit?usp=sharing

Pro-tip: you can create a settings.xml file with these contents:



  flink-1.5.0


  
flink-1.5.0

  
flink-1.5.0


https://repository.apache.org/content/repositories/orgapacheflink-1160/

  
  
archetype


https://repository.apache.org/content/repositories/orgapacheflink-1160/

  

  



And reference that in you maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

[jira] [Created] (FLINK-9415) Remove reference to StreamingMultipleProgramsTestBase in docs

[Thomas Weise (JIRA)]

Thomas Weise created FLINK-9415:
---

 Summary: Remove reference to StreamingMultipleProgramsTestBase in 
docs
 Key: FLINK-9415
 URL: https://issues.apache.org/jira/browse/FLINK-9415
 Project: Flink
  Issue Type: Bug
  Components: Documentation
Affects Versions: 1.5.0
Reporter: Thomas Weise
Assignee: Thomas Weise






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9414) Remove jline-terminal and jline-reader from LICENSE file

[Till Rohrmann (JIRA)]

Till Rohrmann created FLINK-9414:


 Summary: Remove jline-terminal and jline-reader from LICENSE file
 Key: FLINK-9414
 URL: https://issues.apache.org/jira/browse/FLINK-9414
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.5.0, 1.6.0
Reporter: Till Rohrmann
Assignee: Till Rohrmann
 Fix For: 1.5.0


The LICENSE file contains entries for {{jline-reader}} and {{jline-terminal}} 
which are not necessary because we only link against these libraries. 
Therefore, we should remove them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9413) Tasks can fail with PartitionNotFoundException if consumer deployment takes too long

[Till Rohrmann (JIRA)]

Till Rohrmann created FLINK-9413:


 Summary: Tasks can fail with PartitionNotFoundException if 
consumer deployment takes too long
 Key: FLINK-9413
 URL: https://issues.apache.org/jira/browse/FLINK-9413
 Project: Flink
  Issue Type: Bug
  Components: Distributed Coordination
Affects Versions: 1.5.0, 1.6.0
Reporter: Till Rohrmann


{{Tasks}} can fail with a {{PartitionNotFoundException}} if the deployment of 
the producer takes too long. More specifically, if it takes longer than the 
{{taskmanager.network.request-backoff.max}}, then the {{Task}} will give up and 
fail.

The problem is that we calculate the {{InputGateDeploymentDescriptor}} for a 
consuming task once the producer has been assigned a slot but we do not wait 
until it is actually running. The problem should be fixed if we wait until the 
task is in state {{RUNNING}} before assigning the result partition to the 
consumer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release 1.5.0, release candidate #4

[Thomas Weise]

Since we need a new build, can we also include:

https://issues.apache.org/jira/browse/FLINK-9402

Thanks,
Thomas


On Tue, May 22, 2018 at 11:22 AM, Till Rohrmann 
wrote:

> There is another blocker which we should fix with the new RC [1]. There is
> already a PR for the problem.
>
> [1] https://issues.apache.org/jira/browse/FLINK-9408
>
> Cheers,
> Till
>
> On Tue, May 22, 2018 at 12:34 PM, Till Rohrmann 
> wrote:
>
> > Unfortunately, I have to revise my vote to -1, because we found a bug in
> > the request partition state RPC call [1]. This bug lets certain batch
> jobs
> > fail.
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-9406
> >
> > Cheers,
> > Till
> >
> > On Sat, May 19, 2018 at 9:17 AM, Thomas Weise  wrote:
> >
> >> +1
> >>
> >> - verified signatures and hashes
> >> - built Kinesis connector from source archive
> >> - run Kinesis consumer against AWS - PASSED
> >> - run Kinesis consumer against Kinesalite - FAILED
> >> https://issues.apache.org/jira/browse/FLINK-9402
> >>
> >>  Thomas
> >>
> >>
> >> On Thu, May 17, 2018 at 5:50 PM, Till Rohrmann 
> >> wrote:
> >>
> >> > Hi everyone,
> >> >
> >> > Please review and vote on the release candidate #4 for the version
> >> 1.5.0,
> >> > as follows:
> >> > [ ] +1, Approve the release
> >> > [ ] -1, Do not approve the release (please provide specific comments)
> >> >
> >> >
> >> > The complete staging area is available for your review, which
> includes:
> >> > * JIRA release notes [1],
> >> > * the official Apache source release and binary convenience releases
> to
> >> be
> >> > deployed to dist.apache.org [2], which are signed with the key with
> >> > fingerprint 1F302569A96CFFD5 [3],
> >> > * all artifacts to be deployed to the Maven Central Repository [4],
> >> > * source code tag "release-1.5.0-rc3" [5],
> >> >
> >> > Please use this document for coordinating testing efforts: [6]
> >> >
> >> > Since the newly included fixes affect only individual components and
> are
> >> > covered by tests, I will keep the voting period of the RC3 which goes
> at
> >> > least until tomorrow 5:30pm CET. It is adopted by majority approval,
> >> with
> >> > at least 3 PMC affirmative votes.
> >> >
> >> > Thanks,
> >> > Your friendly Release Manager
> >> >
> >> > [1]
> >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> > projectId=12315522=12341764
> >> > [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc4/
> >> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >> > [4] https://repository.apache.org/content/repositories/
> >> > orgapacheflink-1159/
> >> > [5]
> >> > https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
> >> > 953f45316b09072e76f3cf3d37d704a7cb7b32c6
> >> > [6]
> >> > https://docs.google.com/document/d/13evetGNVeGvSufeqC0bcfiHGS_
> >> > v8n06I0p6nEtaQzS4/edit?usp=sharing
> >> >
> >> > Pro-tip: you can create a settings.xml file with these contents:
> >> >
> >> > 
> >> > 
> >> >   flink-1.5.0
> >> > 
> >> > 
> >> >   
> >> > flink-1.5.0
> >> > 
> >> >   
> >> > flink-1.5.0
> >> > 
> >> >
> >> > https://repository.apache.org/content/repositories/
> orgapacheflink-1159/
> >> > 
> >> >   
> >> >   
> >> > archetype
> >> > 
> >> >
> >> > https://repository.apache.org/content/repositories/
> orgapacheflink-1159/
> >> > 
> >> >   
> >> > 
> >> >   
> >> > 
> >> > 
> >> >
> >> > And reference that in you maven commands via --settings
> >> > path/to/settings.xml. This is useful for creating a quickstart based
> on
> >> the
> >> > staged release and for building against the staged jars.
> >> >
> >>
> >
> >
>

Re: [VOTE] Release 1.5.0, release candidate #4

[Till Rohrmann]

There is another blocker which we should fix with the new RC [1]. There is
already a PR for the problem.

[1] https://issues.apache.org/jira/browse/FLINK-9408

Cheers,
Till

On Tue, May 22, 2018 at 12:34 PM, Till Rohrmann 
wrote:

> Unfortunately, I have to revise my vote to -1, because we found a bug in
> the request partition state RPC call [1]. This bug lets certain batch jobs
> fail.
>
> [1] https://issues.apache.org/jira/browse/FLINK-9406
>
> Cheers,
> Till
>
> On Sat, May 19, 2018 at 9:17 AM, Thomas Weise  wrote:
>
>> +1
>>
>> - verified signatures and hashes
>> - built Kinesis connector from source archive
>> - run Kinesis consumer against AWS - PASSED
>> - run Kinesis consumer against Kinesalite - FAILED
>> https://issues.apache.org/jira/browse/FLINK-9402
>>
>>  Thomas
>>
>>
>> On Thu, May 17, 2018 at 5:50 PM, Till Rohrmann 
>> wrote:
>>
>> > Hi everyone,
>> >
>> > Please review and vote on the release candidate #4 for the version
>> 1.5.0,
>> > as follows:
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> >
>> > The complete staging area is available for your review, which includes:
>> > * JIRA release notes [1],
>> > * the official Apache source release and binary convenience releases to
>> be
>> > deployed to dist.apache.org [2], which are signed with the key with
>> > fingerprint 1F302569A96CFFD5 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "release-1.5.0-rc3" [5],
>> >
>> > Please use this document for coordinating testing efforts: [6]
>> >
>> > Since the newly included fixes affect only individual components and are
>> > covered by tests, I will keep the voting period of the RC3 which goes at
>> > least until tomorrow 5:30pm CET. It is adopted by majority approval,
>> with
>> > at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > Your friendly Release Manager
>> >
>> > [1]
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > projectId=12315522=12341764
>> > [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc4/
>> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> > [4] https://repository.apache.org/content/repositories/
>> > orgapacheflink-1159/
>> > [5]
>> > https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
>> > 953f45316b09072e76f3cf3d37d704a7cb7b32c6
>> > [6]
>> > https://docs.google.com/document/d/13evetGNVeGvSufeqC0bcfiHGS_
>> > v8n06I0p6nEtaQzS4/edit?usp=sharing
>> >
>> > Pro-tip: you can create a settings.xml file with these contents:
>> >
>> > 
>> > 
>> >   flink-1.5.0
>> > 
>> > 
>> >   
>> > flink-1.5.0
>> > 
>> >   
>> > flink-1.5.0
>> > 
>> >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1159/
>> > 
>> >   
>> >   
>> > archetype
>> > 
>> >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1159/
>> > 
>> >   
>> > 
>> >   
>> > 
>> > 
>> >
>> > And reference that in you maven commands via --settings
>> > path/to/settings.xml. This is useful for creating a quickstart based on
>> the
>> > staged release and for building against the staged jars.
>> >
>>
>
>

[jira] [Created] (FLINK-9411) Support parquet rolling sink writer

[mingleizhang (JIRA)]

mingleizhang created FLINK-9411:
---

 Summary: Support parquet rolling sink writer
 Key: FLINK-9411
 URL: https://issues.apache.org/jira/browse/FLINK-9411
 Project: Flink
  Issue Type: New Feature
Reporter: mingleizhang
Assignee: Triones Deng


Like support orc rolling sink writer in FLINK-9407 , we should also support 
parquet rolling sink writer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9410) Replace NMClient with NMClientAsync in YarnResourceManager

[Till Rohrmann (JIRA)]

Till Rohrmann created FLINK-9410:


 Summary: Replace NMClient with NMClientAsync in YarnResourceManager
 Key: FLINK-9410
 URL: https://issues.apache.org/jira/browse/FLINK-9410
 Project: Flink
  Issue Type: Improvement
  Components: Distributed Coordination
Affects Versions: 1.5.0, 1.6.0
Reporter: Till Rohrmann
 Fix For: 1.6.0


Currently, the {{YarnResourceManager}} uses the synchronous {{NMClient}} which 
is called from within the main thread of the {{ResourceManager}}. Since these 
operations are blocking, we should replace the client with the 
{{NMClientAsync}} and make the calls non blocking.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9409) Missing assembly-dependencies in flink-dist/pom.xml

[Nico Kruber (JIRA)]

Nico Kruber created FLINK-9409:
--

 Summary: Missing assembly-dependencies in flink-dist/pom.xml
 Key: FLINK-9409
 URL: https://issues.apache.org/jira/browse/FLINK-9409
 Project: Flink
  Issue Type: Improvement
  Components: Build System
Affects Versions: 1.5.0, 1.6.0
Reporter: Nico Kruber
Assignee: Nico Kruber


Building Flink via {{mvn clean install -pl flink-dist -am}} currently fails 
because {{flink-json}} is not defined as a dependency in {{flink-dist/pom.xml}} 
although being used in the assembly.

The same is true for {{flink-avro}} but this seems to be built due to some 
indirect dependency.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-9408) Retry JM-RM connection in case of explicit disconnect

[Till Rohrmann (JIRA)]

Till Rohrmann created FLINK-9408:


 Summary: Retry JM-RM connection in case of explicit disconnect
 Key: FLINK-9408
 URL: https://issues.apache.org/jira/browse/FLINK-9408
 Project: Flink
  Issue Type: Bug
  Components: Distributed Coordination
Affects Versions: 1.5.0, 1.6.0
Reporter: Till Rohrmann
Assignee: Till Rohrmann
 Fix For: 1.5.0


The JM should try to reconnect to the RM not only in the case of a heartbeat 
timeout but also in case of an explicit disconnect.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release 1.5.0, release candidate #4

[Till Rohrmann]

Unfortunately, I have to revise my vote to -1, because we found a bug in
the request partition state RPC call [1]. This bug lets certain batch jobs
fail.

[1] https://issues.apache.org/jira/browse/FLINK-9406

Cheers,
Till

On Sat, May 19, 2018 at 9:17 AM, Thomas Weise  wrote:

> +1
>
> - verified signatures and hashes
> - built Kinesis connector from source archive
> - run Kinesis consumer against AWS - PASSED
> - run Kinesis consumer against Kinesalite - FAILED
> https://issues.apache.org/jira/browse/FLINK-9402
>
>  Thomas
>
>
> On Thu, May 17, 2018 at 5:50 PM, Till Rohrmann 
> wrote:
>
> > Hi everyone,
> >
> > Please review and vote on the release candidate #4 for the version 1.5.0,
> > as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> >
> > The complete staging area is available for your review, which includes:
> > * JIRA release notes [1],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 1F302569A96CFFD5 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.5.0-rc3" [5],
> >
> > Please use this document for coordinating testing efforts: [6]
> >
> > Since the newly included fixes affect only individual components and are
> > covered by tests, I will keep the voting period of the RC3 which goes at
> > least until tomorrow 5:30pm CET. It is adopted by majority approval, with
> > at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Your friendly Release Manager
> >
> > [1]
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12315522=12341764
> > [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc4/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4] https://repository.apache.org/content/repositories/
> > orgapacheflink-1159/
> > [5]
> > https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h=
> > 953f45316b09072e76f3cf3d37d704a7cb7b32c6
> > [6]
> > https://docs.google.com/document/d/13evetGNVeGvSufeqC0bcfiHGS_
> > v8n06I0p6nEtaQzS4/edit?usp=sharing
> >
> > Pro-tip: you can create a settings.xml file with these contents:
> >
> > 
> > 
> >   flink-1.5.0
> > 
> > 
> >   
> > flink-1.5.0
> > 
> >   
> > flink-1.5.0
> > 
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1159/
> > 
> >   
> >   
> > archetype
> > 
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1159/
> > 
> >   
> > 
> >   
> > 
> > 
> >
> > And reference that in you maven commands via --settings
> > path/to/settings.xml. This is useful for creating a quickstart based on
> the
> > staged release and for building against the staged jars.
> >
>

[jira] [Created] (FLINK-9406) Request finished partition state fails due to referential equality comparison

[Till Rohrmann (JIRA)]

Till Rohrmann created FLINK-9406:


 Summary: Request finished partition state fails due to referential 
equality comparison
 Key: FLINK-9406
 URL: https://issues.apache.org/jira/browse/FLINK-9406
 Project: Flink
  Issue Type: Bug
  Components: Distributed Coordination
Affects Versions: 1.5.0, 1.6.0
Reporter: Till Rohrmann
Assignee: Nico Kruber
 Fix For: 1.5.0


The execution of batch jobs can fail because in some cases we cannot retrieve 
the partition state. The problem seems to be that we use referential equality 
in {{JobMaster.java:619}} when requesting the state of a finished result 
partition. This, of course, always fails with a 
{{PartitionProducerDisposedException}} because we should use the proper 
{{equals}} method for the comparison of the {{ResultPartitionID}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Enable GitBox integration (#2)

[Timo Walther]

+1

Am 22.05.18 um 10:49 schrieb Ted Yu:

+1
 Original message From: Chesnay Schepler  
Date: 5/22/18  1:12 AM  (GMT-08:00) To: dev@flink.apache.org Subject: [VOTE] Enable 
GitBox integration (#2)
Hello,

since no concerns have been raised in the discussion about enabling
GitBox [1] I'm opening this vote to make things official.

Please vote on enabling GitBox integration for the flink and flink-web
repositories as follows:

[ ] +1, Approve GitBox
[ ] -1, Do not approve GitBox (please provide specific comments)

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

This is the second attempt for this vote. The previous vote was
cancelled due to the flink-web repository settings. Changes to the
previous vote are highlighted in bold.

If accepted I will file a ticket with INFRA to enable GitBox with the
following settings:

flink:

    * no wiki
    * no issues
    * no projects
    * no merge commit button (rebase/squash merge button still enabled)
    * protected branches [2]: master, release-1.[0-5] (the latter we will
  have to update with each release)

flink-web

    * no wiki
    **no issues*
    * no projects
    * no merge commit button (rebase/squash merge button still enabled)
    * protected branch: asf-site
    * default branch: asf-site (while we're at it...)

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html
[2] https://help.github.com/articles/about-protected-branches/

Re: [VOTE] Enable GitBox integration (#2)

[Nico Kruber]

+1

On 22/05/18 10:12, Chesnay Schepler wrote:
> Hello,
> 
> since no concerns have been raised in the discussion about enabling
> GitBox [1] I'm opening this vote to make things official.
> 
> Please vote on enabling GitBox integration for the flink and flink-web
> repositories as follows:
> 
> [ ] +1, Approve GitBox
> [ ] -1, Do not approve GitBox (please provide specific comments)
> 
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> 
> This is the second attempt for this vote. The previous vote was
> cancelled due to the flink-web repository settings. Changes to the
> previous vote are highlighted in bold.
> 
> If accepted I will file a ticket with INFRA to enable GitBox with the
> following settings:
> 
> flink:
> 
>   * no wiki
>   * no issues
>   * no projects
>   * no merge commit button (rebase/squash merge button still enabled)
>   * protected branches [2]: master, release-1.[0-5] (the latter we will
>     have to update with each release)
> 
> flink-web
> 
>   * no wiki
>   **no issues*
>   * no projects
>   * no merge commit button (rebase/squash merge button still enabled)
>   * protected branch: asf-site
>   * default branch: asf-site (while we're at it...)
> 
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html
> 
> [2] https://help.github.com/articles/about-protected-branches/
> 
> 
> 

-- 
Nico Kruber | Software Engineer
data Artisans

Follow us @dataArtisans
--
Join Flink Forward - The Apache Flink Conference
Stream Processing | Event Driven | Real Time
--
Data Artisans GmbH | Stresemannstr. 121A,10963 Berlin, Germany
data Artisans, Inc. | 1161 Mission Street, San Francisco, CA-94103, USA
--
Data Artisans GmbH
Registered at Amtsgericht Charlottenburg: HRB 158244 B
Managing Directors: Dr. Kostas Tzoumas, Dr. Stephan Ewen



signature.asc
Description: OpenPGP digital signature

Re: [VOTE] Enable GitBox integration (#2)

[Ted Yu]

+1
 Original message From: Chesnay Schepler  
Date: 5/22/18  1:12 AM  (GMT-08:00) To: dev@flink.apache.org Subject: [VOTE] 
Enable GitBox integration (#2) 
Hello,

since no concerns have been raised in the discussion about enabling 
GitBox [1] I'm opening this vote to make things official.

Please vote on enabling GitBox integration for the flink and flink-web 
repositories as follows:

[ ] +1, Approve GitBox
[ ] -1, Do not approve GitBox (please provide specific comments)

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

This is the second attempt for this vote. The previous vote was 
cancelled due to the flink-web repository settings. Changes to the 
previous vote are highlighted in bold.

If accepted I will file a ticket with INFRA to enable GitBox with the 
following settings:

flink:

   * no wiki
   * no issues
   * no projects
   * no merge commit button (rebase/squash merge button still enabled)
   * protected branches [2]: master, release-1.[0-5] (the latter we will
 have to update with each release)

flink-web

   * no wiki
   **no issues*
   * no projects
   * no merge commit button (rebase/squash merge button still enabled)
   * protected branch: asf-site
   * default branch: asf-site (while we're at it...)

[1] 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html
[2] https://help.github.com/articles/about-protected-branches/

Re: [VOTE] Enable GitBox integration (#2)

[Dawid Wysakowicz]

+1

On 22/05/18 10:12, Chesnay Schepler wrote:
> Hello,
>
> since no concerns have been raised in the discussion about enabling
> GitBox [1] I'm opening this vote to make things official.
>
> Please vote on enabling GitBox integration for the flink and flink-web
> repositories as follows:
>
> [ ] +1, Approve GitBox
> [ ] -1, Do not approve GitBox (please provide specific comments)
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> This is the second attempt for this vote. The previous vote was
> cancelled due to the flink-web repository settings. Changes to the
> previous vote are highlighted in bold.
>
> If accepted I will file a ticket with INFRA to enable GitBox with the
> following settings:
>
> flink:
>
>   * no wiki
>   * no issues
>   * no projects
>   * no merge commit button (rebase/squash merge button still enabled)
>   * protected branches [2]: master, release-1.[0-5] (the latter we will
>     have to update with each release)
>
> flink-web
>
>   * no wiki
>   **no issues*
>   * no projects
>   * no merge commit button (rebase/squash merge button still enabled)
>   * protected branch: asf-site
>   * default branch: asf-site (while we're at it...)
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html
> [2] https://help.github.com/articles/about-protected-branches/
>
>
>

[VOTE] Enable GitBox integration (#2)

[Chesnay Schepler]

Hello,

since no concerns have been raised in the discussion about enabling 
GitBox [1] I'm opening this vote to make things official.


Please vote on enabling GitBox integration for the flink and flink-web 
repositories as follows:


[ ] +1, Approve GitBox
[ ] -1, Do not approve GitBox (please provide specific comments)

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.


This is the second attempt for this vote. The previous vote was 
cancelled due to the flink-web repository settings. Changes to the 
previous vote are highlighted in bold.


If accepted I will file a ticket with INFRA to enable GitBox with the 
following settings:


flink:

  * no wiki
  * no issues
  * no projects
  * no merge commit button (rebase/squash merge button still enabled)
  * protected branches [2]: master, release-1.[0-5] (the latter we will
have to update with each release)

flink-web

  * no wiki
  **no issues*
  * no projects
  * no merge commit button (rebase/squash merge button still enabled)
  * protected branch: asf-site
  * default branch: asf-site (while we're at it...)

[1] 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html

[2] https://help.github.com/articles/about-protected-branches/

[CANCELED][VOTE] Enable GitBox integration

[Chesnay Schepler]

That's a good point, I'll start another vote. Let's stick to the 
existing process.


On 22.05.2018 09:49, Dawid Wysakowicz wrote:

-1

The only reason why -1 is I don't see a point in enabling issues for
flink-web. We already track them in Jira and I think adding another
channel for it will make tracking issues only harder.

With issues disabled for flink-web I vote +1.

On 22/05/18 09:32, Chesnay Schepler wrote:

Hello,

since no concerns have been raised in the discussion about enabling
GitBox [1] I'm opening this vote to make things official.

Please vote on enabling GitBox integration for the flink and flink-web
repositories as follows:

[ ] +1, Approve GitBox
[ ] -1, Do not approve GitBox (please provide specific comments)

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

If accepted I will file a ticket with INFRA to enable GitBox with the
following settings:

flink:

  * no wiki
  * no issues
  * no projects
  * no merge commit button (rebase/squash merge button still enabled)
  * protected branches [2]: master, release-1.[0-5] (the latter we will
have to update with each release)

flink-web

  * no wiki
  * issues enabled
  * no projects
  * no merge commit button (rebase/squash merge button still enabled)
  * protected branch: asf-site
  * default branch: asf-site (while we're at it...)

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html
[2] https://help.github.com/articles/about-protected-branches/

Re: [VOTE] Enable GitBox integration

[Dawid Wysakowicz]

-1

The only reason why -1 is I don't see a point in enabling issues for
flink-web. We already track them in Jira and I think adding another
channel for it will make tracking issues only harder.

With issues disabled for flink-web I vote +1.

On 22/05/18 09:32, Chesnay Schepler wrote:
> Hello,
>
> since no concerns have been raised in the discussion about enabling
> GitBox [1] I'm opening this vote to make things official.
>
> Please vote on enabling GitBox integration for the flink and flink-web
> repositories as follows:
>
> [ ] +1, Approve GitBox
> [ ] -1, Do not approve GitBox (please provide specific comments)
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> If accepted I will file a ticket with INFRA to enable GitBox with the
> following settings:
>
> flink:
>
>  * no wiki
>  * no issues
>  * no projects
>  * no merge commit button (rebase/squash merge button still enabled)
>  * protected branches [2]: master, release-1.[0-5] (the latter we will
>    have to update with each release)
>
> flink-web
>
>  * no wiki
>  * issues enabled
>  * no projects
>  * no merge commit button (rebase/squash merge button still enabled)
>  * protected branch: asf-site
>  * default branch: asf-site (while we're at it...)
>
> [1]
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html
> [2] https://help.github.com/articles/about-protected-branches/
>

[VOTE] Enable GitBox integration

[Chesnay Schepler]

Hello,

since no concerns have been raised in the discussion about enabling 
GitBox [1] I'm opening this vote to make things official.


Please vote on enabling GitBox integration for the flink and flink-web 
repositories as follows:


[ ] +1, Approve GitBox
[ ] -1, Do not approve GitBox (please provide specific comments)

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.


If accepted I will file a ticket with INFRA to enable GitBox with the 
following settings:


flink:

 * no wiki
 * no issues
 * no projects
 * no merge commit button (rebase/squash merge button still enabled)
 * protected branches [2]: master, release-1.[0-5] (the latter we will
   have to update with each release)

flink-web

 * no wiki
 * issues enabled
 * no projects
 * no merge commit button (rebase/squash merge button still enabled)
 * protected branch: asf-site
 * default branch: asf-site (while we're at it...)

[1] 
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-GitBox-td22328.html

[2] https://help.github.com/articles/about-protected-branches/

Increasing Disk Read Throughput and IOPS

[Govindarajan Srinivasaraghavan]

Hi All,

We are running flink in AWS and we are observing a strange behavior. We are
using docker containers, EBS for storage and Rocks DB state backend. We
have a few map and value states with checkpointing every 30 seconds and
incremental checkpointing turned on. The issue we are noticing is the read
IOPS and read throughput gradually increases over time and keeps constantly
growing. The write throughput and write bytes are not increasing as much as
reads. The checkpoints are written to a durable NFS storage. We are not
sure what is causing this constant increase in read throughput but due to
which we are running out of EBS burst balance and need to restart the job
every once in a while. Attached the EBS read and write metrics. Has anyone
encountered this issue and what could be the possible solution.


We have also tried setting the below rocksdb options but didn't help.


DBOptions:

currentOptions.setOptimizeFiltersForHits(true)
.setWriteBufferSize(536870912)
.setMaxWriteBufferNumber(5)
.setMinWriteBufferNumberToMerge(2);

ColumnFamilyOptions:

currentOptions.setMaxBackgroundCompactions(4)
.setMaxManifestFileSize(1048576)
.setMaxLogFileSize(1048576);



Thanks.