[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-25 Thread Till Rohrmann (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16555838#comment-16555838
 ] 

Till Rohrmann commented on FLINK-4319:
--

# FLINK-9953 is the issue for the active Kubernetes integration (first mode), 
FLINK-7087 is the parent issue for the passive container mode (second mode)
# The release date is not yet fixed since the community first needs to finish 
the current release. The community usually releases every 3 months a new major 
Flink version
# Unfortunately, we don't have a proper design document yet. This will be one 
of the first tasks to be done after the {{1.6.0}} release.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-23 Thread Yinan Li (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553111#comment-16553111
 ] 

Yinan Li commented on FLINK-4319:
-

Thanks for the detailed answers again, [~till.rohrmann]! A couple of more 
questions:
 # What's the umbrella Jira for work on the first operation mode, and what's 
the Jira for adaptive scaling for the second mode?  
 # What's the estimated time for the next release? 

Thanks!

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-23 Thread Till Rohrmann (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552448#comment-16552448
 ] 

Till Rohrmann commented on FLINK-4319:
--

# I think there are good use cases for both modes and, thus, hope that the 
community will add both of them. Better container/Kubernetes support is very 
high on the priority list of the community and, thus, I would expect that this 
happens very soon. Personally I hope that we can offer both modes with the next 
release.
# Adaptive scaling should be the next step of improving the existing container 
mode (second operation mode). I hope that we can finish this feature with the 
next release.
# Yes
# The documentation you can find 
[here|https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/kubernetes.html]
 refers to setting up a session cluster in the second operation mode. There is 
some more documentation how to set up a per-job cluster in the same mode 
[here|https://github.com/apache/flink/blob/master/flink-container/kubernetes/README.md]

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-22 Thread Yinan Li (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552331#comment-16552331
 ] 

Yinan Li commented on FLINK-4319:
-

Thanks for the information, [~till.rohrmann]! Got a few more questions below:
 # What's the plan for the two operation modes moving forward? Will both of 
them be supported in the long term?
 # What's the estimated time when adaptive scaling will be added into the 
second operation mode?
 # Is the second operation mode primarily for running a single job per 
deployment? 
 # Is the latest documentation on setting up a Flink cluster on Kubernetes 
referring to the second mode?

Thanks!

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-22 Thread Till Rohrmann (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552024#comment-16552024
 ] 

Till Rohrmann commented on FLINK-4319:
--

Hi [~liyinan926], Flink's Kubernetes support is not yet fully completed and the 
community is still working on it.

There are actually two operation modes which we would like to support. The 
first one is similar to Flink's Yarn and Mesos integration where the 
{{ResourceManager}} is able to talk to the Kubernetes master to start new pods 
if needed. I actually have a dev branch where I prototyped a 
{{KubernetesResourceManager}} which you can find 
[here|https://github.com/tillrohrmann/flink/tree/nativeKubernetes].

The other mode builds on FLINK-7087 and moves the responsibility of allocating 
new resources/pods to the user. In this mode, the {{ResourceManager}} won't 
start new {{TaskExecutors}} but simply accepts all slots from running 
{{TaskExecutors}} and advertises them to the {{JobMaster}}. The {{JobMaster}} 
will then scale the job to the currently available number of slots. That way 
the user can decide whether his job needs some more resources by starting new 
pods (with a {{TaskExecutor}}) or less resources by stopping pods.

At the moment, the latter mode only works without the adaptive scaling of jobs. 
This means that one can start the job with a determined parallelism and then 
one has to make sure that there are enough {{TaskExecutors}} which offer enough 
slots to execute the job.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-20 Thread Yinan Li (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16551321#comment-16551321
 ] 

Yinan Li commented on FLINK-4319:
-

Interested in bring FLIP-6 for Flink on Kubernetes. Wondering why the design 
for deployment on Kubernetes is very different from the other cluster managers. 
It looks like to me that users have to start a static number of TaskManagers 
and the ResourceManager is not responsible for dynamically spawning new 
TaskManagers on Kubernetes. If this is the case (correct me if I'm wrong), 
what's the reason for this design?

P.S. I also work on the native Kubernetes scheduler backend for Spark.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
> Fix For: 1.5.0
>
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-13 Thread Till Rohrmann (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542596#comment-16542596
 ] 

Till Rohrmann commented on FLINK-4319:
--

[~yazdanjs] thanks for your interest. The community implemented a good part of 
the whole Flip-6 effort. I think we can actually close the linked issues here.

However, there are still plenty of open issues and potential improvements which 
one could apply to Flink's distributed architecture. Most of these issues are 
assigned to the `Distributed Coordination` component. Please look for issues 
assigned to this component.

I will update the old Flip-6 JIRA issues to reflect the current state.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2018-07-11 Thread Yazdan Shirvany (JIRA)


[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16540220#comment-16540220
 ] 

Yazdan Shirvany commented on FLINK-4319:


[~till.rohrmann] I am very interested to start contributing in this effort and 
I am wondering where should I start. I would appreciate if you guide me here 
and let me know which task/subtask is good to start inorder to understand the 
whole picture as well as be able to contribute :)

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>Priority: Major
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



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


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-21 Thread Till Rohrmann (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175658#comment-16175658
 ] 

Till Rohrmann commented on FLINK-4319:
--

Hi [~suez1224],

thanks for testing out the current state of Flip-6. This is valuable feedback 
which we have to address.

1) It's true that we don't wait on the completion of the {{JobMaster}} shutdown 
in the {{JobManagerRunner}} yet. However, I thought that the 
{{JobClusterEntrypoint}} should call {{System.exit}} upon termination of the 
job (at least eventually). This might point towards a bug.
2) The RM stops TMs after they were idle for a certain time (10s). However, the 
stopping logic is not yet implemented for the {{YarnResourceManager}}. See 
YarnResourceManager.java:231. This should be fairly straight forward. See 
FLINK-7076 for more information.
3) We are currently working on porting the web dashboard to the new 
architecture. See FLINK-7530 for the current state.

If you like, then you could take over FLINK-7076 since we didn't make much 
progress there. Also FLINK-7530 could benefit from helping hands :-)


> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-21 Thread Shuyi Chen (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175494#comment-16175494
 ] 

Shuyi Chen commented on FLINK-4319:
---

Hi [~till.rohrmann], thanks a lot for the pointers.
I was trying out the current status of Flip-6 flink-on-yarn. I found several 
problems:
1) JobMaster wont get killed after the job is finished. It seems the JobMaster 
never received the SHUTDOWN akka message. Maybe it's related to 
https://issues.apache.org/jira/browse/FLINK-5176?
2) The TaskManager wont get released after the job died. Maybe this is related 
to 1).
3) The web dashboard is no longer accessible. 

Can you shed some lights on these issues? I would be happy to help if needed. 
Thanks.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-11 Thread Ashish Pokharel (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161107#comment-16161107
 ] 

Ashish Pokharel commented on FLINK-4319:


Thanks Till - this ia great.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-11 Thread Till Rohrmann (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160890#comment-16160890
 ] 

Till Rohrmann commented on FLINK-4319:
--

Hi Ashish,

great to hear that things are working so far :-)

Dynamic scaling will be part of the Flip-6 work. With Flip-6 we will offer a 
API call to scale up/down running jobs. Some of the code is already merged into 
master and we are currently working on merging the rest. We hope to get it all 
in for Flink 1.4. 

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-10 Thread Ashish Pokharel (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160596#comment-16160596
 ] 

Ashish Pokharel commented on FLINK-4319:


Hi All,
We currently have a few Flink applications running in our Production 
environment and things are great. Great job keeping this project awesome!
As we start deploying more Applications, I am pretty sure we will hit resource 
allocation issues very soon. That prompted to research dynamic allocation in 
Flink and I got routed to this from FLIP-6. Is dynamic allocation still in 
scope and if so, when can we expect anything along those lines? Pretty much all 
of our Apps are streaming and always running - which makes it even more 
essential to be able to grow/shrink slot dynamically. Only other option I can 
think of right now and starting a Parent Job to pool together Apps that are 
staggered enough (even though they are streaming).

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-02 Thread Till Rohrmann (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151599#comment-16151599
 ] 

Till Rohrmann commented on FLINK-4319:
--

Hi [~suez1224],

if you want to integrate Flink with a new cluster resource scheduler, then I 
would recommend taking a look at the {{ResourceManager}} class. This class and 
its subclasses {{YarnResourceManager}} and {{MesosResourceManager}} are the 
touch point between Flink and the respective cluster resource manager. Let me 
know if you have more questions.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-09-01 Thread Shuyi Chen (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16151309#comment-16151309
 ] 

Shuyi Chen commented on FLINK-4319:
---

Hi Till,

I am looking into integrating Flink with an internal cluster resource 
scheduler, which will be open-sourced. I would like to help the development on 
Flip-6, and at the same time, look into how we can integrate our cluster 
resource scheduler with Flink. Could you please point me to where I can start 
with, and help? Thanks a lot.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-08-22 Thread Till Rohrmann (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137075#comment-16137075
 ] 

Till Rohrmann commented on FLINK-4319:
--

Hi Bowen,

development of Flip-6 is already under way for quite some time and we have 
already made some really good progress. We hope to get the rework done with the 
Flink 1.4 release. What we are currently working on are the REST endpoints, 
reach functional parity with the existing code base and thorough tests of the 
new components. Every helping hand is highly welcome :-)

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>Assignee: Till Rohrmann
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-08-22 Thread Bowen Li (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16137064#comment-16137064
 ] 

Bowen Li commented on FLINK-4319:
-

Hi guys, what's the schedule for this task? When are we starting, and what's 
the target release?

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>  Labels: flip-6
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-04-18 Thread Till Rohrmann (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972639#comment-15972639
 ] 

Till Rohrmann commented on FLINK-4319:
--

Thanks for sharing [~sedgewickmm18] :-)

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-04-08 Thread JIRA

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15961748#comment-15961748
 ] 

Markus Müller commented on FLINK-4319:
--

For a reference implementation on Bluemix with kubernetes support in beta, 
please have a look at github.com/sedgewickmm18/After-HadoopsummitMeetupIoT  - 
it should work on all platforms with kubernetes support.
I'm waiting for FLIP-6 to implement multi-tenancy support, i.e. to have task 
managers dedicated to tenants and thus isolate tenant workload

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-03-27 Thread Stephan Ewen (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943212#comment-15943212
 ] 

Stephan Ewen commented on FLINK-4319:
-

Flink on Kubernetes works today already. We need FLIP-6 only for elasticity in 
service resource scaling.

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (FLINK-4319) Rework Cluster Management (FLIP-6)

2017-03-27 Thread shijinkui (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943198#comment-15943198
 ] 

shijinkui commented on FLINK-4319:
--

Flink on Kubernetes, do we have some schedule?

> Rework Cluster Management (FLIP-6)
> --
>
> Key: FLINK-4319
> URL: https://issues.apache.org/jira/browse/FLINK-4319
> Project: Flink
>  Issue Type: Improvement
>  Components: Cluster Management
>Affects Versions: 1.1.0
>Reporter: Stephan Ewen
>
> This is the root issue to track progress of the rework of cluster management 
> (FLIP-6) 
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65147077



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)