[jira] [Created] (FLINK-14463) Merge Handover in flink-connector-kafka and flink-connector-kafka-0.9

2019-10-19 Thread Jiayi Liao (Jira)
Jiayi Liao created FLINK-14463:
--

 Summary: Merge Handover in flink-connector-kafka and 
flink-connector-kafka-0.9
 Key: FLINK-14463
 URL: https://issues.apache.org/jira/browse/FLINK-14463
 Project: Flink
  Issue Type: Improvement
Affects Versions: 1.9.0
Reporter: Jiayi Liao


Handover.java exists both in flink-connector-kafka(kafka 2.x) module and 
flink-connector-kafka-0.9 module. We should put this file into kafka base 
module to avoid repeated codes.

cc [~sewen] [~yanghua]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-14462) Remove JobGraph#allowQueuedScheduling flag because it is always true

2019-10-19 Thread Zili Chen (Jira)
Zili Chen created FLINK-14462:
-

 Summary: Remove JobGraph#allowQueuedScheduling flag because it is 
always true
 Key: FLINK-14462
 URL: https://issues.apache.org/jira/browse/FLINK-14462
 Project: Flink
  Issue Type: Sub-task
  Components: Runtime / Configuration
Affects Versions: 1.10.0
Reporter: Zili Chen
Assignee: Zili Chen
 Fix For: 1.10.0


CC [~trohrmann][~zhuzh]

The only point {{#setAllowQueuedScheduling(false)}} is in 
{{JobGraphGenerator}}. IIRC we always {{#setAllowQueuedScheduling(true)}} after 
the generation and before the submission. For reduce confusion I propose to 
remove {{JobGraph#allowQueuedScheduling}} and refactor the related logic to all 
respect {{true}}.

This flag is originally used for configuring different resource allocation 
strategy between legacy mode and FLIP-6 arch. And there remains branches in 
{{Scheduler}} which might cause further confusion.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-14461) Remove unused sessionTimeout from JobGraph

2019-10-19 Thread Zili Chen (Jira)
Zili Chen created FLINK-14461:
-

 Summary: Remove unused sessionTimeout from JobGraph
 Key: FLINK-14461
 URL: https://issues.apache.org/jira/browse/FLINK-14461
 Project: Flink
  Issue Type: Improvement
  Components: Runtime / Configuration
Affects Versions: 1.10.0
Reporter: Zili Chen
Assignee: Zili Chen
 Fix For: 1.10.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [ANNOUNCE] Apache Flink 1.9.1 released

2019-10-19 Thread Hequn Cheng
Thanks a lot to Jark, Jincheng, and everyone that make this release
possible.

Best, Hequn

On Sat, Oct 19, 2019 at 10:29 PM Zili Chen  wrote:

> Thanks a lot for being release manager Jark. Great work!
>
> Best,
> tison.
>
>
> Till Rohrmann  于2019年10月19日周六 下午10:15写道:
>
>> Thanks a lot for being our release manager Jark and thanks to everyone
>> who has helped to make this release possible.
>>
>> Cheers,
>> Till
>>
>> On Sat, Oct 19, 2019 at 3:26 PM Jark Wu  wrote:
>>
>>>  Hi,
>>>
>>> The Apache Flink community is very happy to announce the release of
>>> Apache Flink 1.9.1, which is the first bugfix release for the Apache Flink
>>> 1.9 series.
>>>
>>> Apache Flink® is an open-source stream processing framework for
>>> distributed, high-performing, always-available, and accurate data streaming
>>> applications.
>>>
>>> The release is available for download at:
>>> https://flink.apache.org/downloads.html
>>>
>>> Please check out the release blog post for an overview of the
>>> improvements for this bugfix release:
>>> https://flink.apache.org/news/2019/10/18/release-1.9.1.html
>>>
>>> The full release notes are available in Jira:
>>> https://issues.apache.org/jira/projects/FLINK/versions/12346003
>>>
>>> We would like to thank all contributors of the Apache Flink community
>>> who helped to verify this release and made this release possible!
>>> Great thanks to @Jincheng for helping finalize this release.
>>>
>>> Regards,
>>> Jark Wu
>>>
>>


Re: [ANNOUNCE] Apache Flink 1.9.1 released

2019-10-19 Thread Zili Chen
Thanks a lot for being release manager Jark. Great work!

Best,
tison.


Till Rohrmann  于2019年10月19日周六 下午10:15写道:

> Thanks a lot for being our release manager Jark and thanks to everyone who
> has helped to make this release possible.
>
> Cheers,
> Till
>
> On Sat, Oct 19, 2019 at 3:26 PM Jark Wu  wrote:
>
>>  Hi,
>>
>> The Apache Flink community is very happy to announce the release of
>> Apache Flink 1.9.1, which is the first bugfix release for the Apache Flink
>> 1.9 series.
>>
>> Apache Flink® is an open-source stream processing framework for
>> distributed, high-performing, always-available, and accurate data streaming
>> applications.
>>
>> The release is available for download at:
>> https://flink.apache.org/downloads.html
>>
>> Please check out the release blog post for an overview of the
>> improvements for this bugfix release:
>> https://flink.apache.org/news/2019/10/18/release-1.9.1.html
>>
>> The full release notes are available in Jira:
>> https://issues.apache.org/jira/projects/FLINK/versions/12346003
>>
>> We would like to thank all contributors of the Apache Flink community who
>> helped to verify this release and made this release possible!
>> Great thanks to @Jincheng for helping finalize this release.
>>
>> Regards,
>> Jark Wu
>>
>


Re: [ANNOUNCE] Apache Flink 1.9.1 released

2019-10-19 Thread Till Rohrmann
Thanks a lot for being our release manager Jark and thanks to everyone who
has helped to make this release possible.

Cheers,
Till

On Sat, Oct 19, 2019 at 3:26 PM Jark Wu  wrote:

>  Hi,
>
> The Apache Flink community is very happy to announce the release of Apache
> Flink 1.9.1, which is the first bugfix release for the Apache Flink 1.9
> series.
>
> Apache Flink® is an open-source stream processing framework for
> distributed, high-performing, always-available, and accurate data streaming
> applications.
>
> The release is available for download at:
> https://flink.apache.org/downloads.html
>
> Please check out the release blog post for an overview of the improvements
> for this bugfix release:
> https://flink.apache.org/news/2019/10/18/release-1.9.1.html
>
> The full release notes are available in Jira:
> https://issues.apache.org/jira/projects/FLINK/versions/12346003
>
> We would like to thank all contributors of the Apache Flink community who
> helped to verify this release and made this release possible!
> Great thanks to @Jincheng for helping finalize this release.
>
> Regards,
> Jark Wu
>


[ANNOUNCE] Apache Flink 1.9.1 released

2019-10-19 Thread Jark Wu
 Hi,

The Apache Flink community is very happy to announce the release of Apache
Flink 1.9.1, which is the first bugfix release for the Apache Flink 1.9
series.

Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
applications.

The release is available for download at:
https://flink.apache.org/downloads.html

Please check out the release blog post for an overview of the improvements
for this bugfix release:
https://flink.apache.org/news/2019/10/18/release-1.9.1.html

The full release notes are available in Jira:
https://issues.apache.org/jira/projects/FLINK/versions/12346003

We would like to thank all contributors of the Apache Flink community who
helped to verify this release and made this release possible!
Great thanks to @Jincheng for helping finalize this release.

Regards,
Jark Wu


[jira] [Created] (FLINK-14460) Active Kubernetes integration phase2 - Production Optimization

2019-10-19 Thread Yang Wang (Jira)
Yang Wang created FLINK-14460:
-

 Summary: Active Kubernetes integration phase2 - Production 
Optimization
 Key: FLINK-14460
 URL: https://issues.apache.org/jira/browse/FLINK-14460
 Project: Flink
  Issue Type: Improvement
Reporter: Yang Wang


This is phase2 of active kubernetes integration. It is a umbrella jira to track 
all production optimization features.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (FLINK-14459) Python module build hangs

2019-10-19 Thread Hequn Cheng (Jira)
Hequn Cheng created FLINK-14459:
---

 Summary: Python module build hangs
 Key: FLINK-14459
 URL: https://issues.apache.org/jira/browse/FLINK-14459
 Project: Flink
  Issue Type: Bug
  Components: API / Python
Affects Versions: 1.9.0, 1.10.0, 1.9.1
Reporter: Hequn Cheng


The build of python module hangs when installing conda. See travis log: 
https://api.travis-ci.org/v3/job/599704570/log.txt

Can't reproduce it neither on my local mac nor on my repo with travis. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: [SURVEY] Dropping non Credit-based Flow Control

2019-10-19 Thread Zhu Zhu
+1 to drop the non credit-based flow control.
We have turned to credit-based flow control for long in production. It has
been good for all our cases.
The non credit-based flow control code has been a burden when we are trying
to change the network stack code for new features.

Thanks,
Zhu Zhu


Biao Liu  于2019年10月10日周四 下午5:45写道:

> Thanks for start this survey, Piotr.
>
> We have benefitted from credit-based flow control a lot. I can't figure out
> a reason to use non credit-based model.
> I think we have kept the older code paths long enough (1.5 -> 1.9). That's
> a big burden to maintain. Especially there are a lot duplicated codes
> between credit-based and non credit-based model.
>
> So +1 to do the cleanup.
>
> Thanks,
> Biao /'bɪ.aʊ/
>
>
>
> On Thu, 10 Oct 2019 at 11:15, zhijiang  .invalid>
> wrote:
>
> > Thanks for bringing this survey Piotr.
> >
> > Actually I was also trying to dropping the non credit-based code path
> from
> > release-1.9, and now I think it is the proper time to do it motivated by
> > [3].
> > The credit-based mode is as default from Flink 1.5 and it has been
> > verified to be stable and reliable in many versions. In Alibaba we are
> > always using the default credit-based mode in all products.
> > It can reduce much overhead of maintaining non credit-based code path, so
> > +1 from my side to drop it.
> >
> > Best,
> > Zhijiang
> > --
> > From:Piotr Nowojski 
> > Send Time:2019年10月2日(星期三) 17:01
> > To:dev 
> > Subject:[SURVEY] Dropping non Credit-based Flow Control
> >
> > Hi,
> >
> > In Flink 1.5 we have introduced Credit-based Flow Control [1] in the
> > network stack. Back then we were aware about potential downsides of it
> [2]
> > and we decided to keep the old model in the code base ( configurable by
> > setting  `taskmanager.network.credit-model: false` ). Now, that we are
> > about to modify internals of the network stack again [3], it might be a
> > good time to clean up the code and remove the older code paths.
> >
> > Is anyone still using the non default non Credit-based model (
> > `taskmanager.network.credit-model: false`)? If so, why?
> >
> > Piotrek
> >
> > [1] https://flink.apache.org/2019/06/05/flink-network-stack.html <
> > https://flink.apache.org/2019/06/05/flink-network-stack.html>
> > [2]
> >
> https://flink.apache.org/2019/06/05/flink-network-stack.html#what-do-we-gain-where-is-the-catch
> > <
> >
> https://flink.apache.org/2019/06/05/flink-network-stack.html#what-do-we-gain-where-is-the-catch
> > >
> > [3]
> >
> https://lists.apache.org/thread.html/a2b58b7b2b24b9bd4814b2aa51d2fc44b08a919eddbb5b1256be5b6a@%3Cdev.flink.apache.org%3E
> > <
> >
> https://lists.apache.org/thread.html/a2b58b7b2b24b9bd4814b2aa51d2fc44b08a919eddbb5b1256be5b6a@%3Cdev.flink.apache.org%3E
> > >
> >
> >
>